Author Topic: State of play - Visual Studio 2010 Full/Express  (Read 2265 times)

0 Members and 1 Guest are viewing this topic.

Glenn R

  • Guest
State of play - Visual Studio 2010 Full/Express
« on: March 15, 2011, 11:21:07 AM »
I'm giving serious thought to using this exclusively, so I thought I would ask some questions first:

1. Who's using it?
2. What version of AutoCAD are you building for?
3. What .NET Framework version are you targeting?
4. Any problems or gotchas?
5. Tips from early adopters?

Cheers,
Glenn.

mohnston

  • Bull Frog
  • Posts: 305
  • CAD Programmer
Re: State of play - Visual Studio 2010 Full/Express
« Reply #1 on: March 15, 2011, 11:41:45 AM »
I've been using VS 2010 (full) exclusively for many months now.
I have written for AutoCAD 2008 and 2011.
I have targeted .NET 2.0 and 3.5 in my projects.

Some issues I remember during conversion:
1. It wants to convert any project you open to a 2010 project. I does offer to back up the existing project first.
2. Edit and continue stopped working which was a deal-breaker for me. However, I found this help at Kean's blog. http://through-the-interface.typepad.com/through_the_interface/2010/04/hitting-breakpoints-in-net-class-libraries-while-debugging-with-visual-studio-2010.html

I like it.
It's amazing what you can do when you don't know what you can't do.
CAD Programming Solutions

vegbruiser

  • Guest
Re: State of play - Visual Studio 2010 Full/Express
« Reply #2 on: March 15, 2011, 11:48:28 AM »
1. Me
2. Inventor 2011/AutoCAD 2009-2011/Civil 3D 2009 depending on which way the wind is blowing and which application I happen to be looking at..
3. .NET 3.5
4. The AutoCAD .NET Wizards don't install correctly on Windows 7 64-bit - at least, they didn't for me. I did fix it manually and can share the details here if necessary.
5. There are a lot of useful extensions that help make VS2010 more polished (PowerCommands for VS 2010 for instance).

Cheers,

Alex.

EDIT: I second mohnston's point about the breakpoints - solution 2 worked for me, but solution 3 offers a "meddle-free" approach in that you don't have to edit .config files.
« Last Edit: March 15, 2011, 11:53:09 AM by AlexF »

pkohut

  • Bull Frog
  • Posts: 483
Re: State of play - Visual Studio 2010 Full/Express
« Reply #3 on: March 15, 2011, 01:52:55 PM »
VS 2010 SP1 was released on 3-3, which may resolve the breakpoint issue.
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=75568AA6-8107-475D-948A-EF22627E57A5
« Last Edit: March 15, 2011, 01:58:12 PM by pkohut »
New tread (not retired) - public repo at https://github.com/pkohut

adalea03

  • Guest
Re: State of play - Visual Studio 2010 Full/Express
« Reply #4 on: March 18, 2011, 12:07:22 PM »
I would sure like some pointers on how to get started using it.
Any learning resources regarding AutoCad would be appreciated as well.
Thanks,
Tony

Draftek

  • Guest
Re: State of play - Visual Studio 2010 Full/Express
« Reply #5 on: March 18, 2011, 01:12:01 PM »
I'm looking at vs2010 for AutoCAD 2012.

What the heck happened to Visual Studio Standard?


huiz

  • Swamp Rat
  • Posts: 917
  • Certified Prof C3D
Re: State of play - Visual Studio 2010 Full/Express
« Reply #6 on: March 19, 2011, 03:39:38 AM »
I use VB.NET 2010 Expres and AutoCAD 2011, target 3.5 Framework (AutoCAD 2012 will work with 4.0 I think) and it works all fine. Also debugging is possible, only that you should edit the acad.exe.config for that.

If I compare the differences between the Express and the VS full version, I really don't know what they're talking about what is possible in the full version and not in the Express version, so I assume I don't need the full version :-)

The conclusion is justified that the initialization of the development of critical subsystem optimizes the probability of success to the development of the technical behavior over a given period.

bkmkh

  • Guest
Re: State of play - Visual Studio 2010 Full/Express
« Reply #7 on: March 22, 2011, 08:32:08 PM »
- What version of AutoCAD are you building for?

 AutoCAD 2010/2011 - Map 2010/2011

- What .NET Framework version are you targeting?

 3.5

- Any problems or gotchas?

 Conversion of VS2008 projects didn't always go smoothly - don't have the details on those to hand anymore
 Had the FileTracker.dll bug pop up http://social.msdn.microsoft.com/Forums/eu/csharpide/thread/88db71cf-a501-428d-91fa-1535d82d8014
 Debugging issues, requiring modification of acad.exe.config

« Last Edit: March 22, 2011, 08:36:07 PM by bkmkh »