so for this year same as before just open the project and specify a new search folder path for all the com and .net dlls from autodesk then change the application class whatever to 9.0? anything else that maybe tricky like one of the other year if i remember right.
just asking this so to be sure and carry on with upgrading later tonight.
oh, also for 2012 is it possible to ditch all com and move to .net? is it as good as autocad .net exposure now? look forward to that.
still no multicore support i guess. render my new computer quite useless compared to core 2 even. got more than 13pt on cinebench doesn't mean much when comes to civil 3d.
Moving to 2012 is pretty much as you describe. If you are using VS2010, I believe you can complie for .NET4.0. If using VS2008 and want to Debug in 2012, there are some things you need to do....I think Kean Walmsley outlined this shortly after the 2012 release.
No, not fully ported to .NET so COM is still needed....but, it is getting better. Especially Surfaces for 2012.
Oh, there was one big issue....not sure if they corrected the SP1 download, but after installing SP1 for C3D2012 the COM references were no longer able to be located. I was sent a REG file to install which fixed this, so if you run into this issue, just let me know and I'll get that REG file to you. (A search back in this forum to around the time the SP was released will give you all the details.)
i got it upgraded ok but can't debug. says
no symbols are loaded for any call stack frame. the source code cannot be displayed
to investigate further
browse to find source
also still says can't debug in x64. should i set project to x64 not any cpu?
I'm not Jeff, but I'm here at the moment
If you upgrade your projects to 2012 you should also change the Framework to 4.0, look to Jeff's post 2 of 4 in this thread.
As long as you haven't changed (or did some tricks with acad.exe.config) you have no chance to get it into the debugger to stop at breakpoints.
>> also still says can't debug in x64
Is that the exact message? Or does VS tell you "you can't EDIT in 64bit mode"?
If the message is "you can't edit" than it's a fact of VS2010 and 64bit ... there is no chance to edit-while-debug. Sorry.
- alfred -
No, leave it set at AnyCPU. You should be able to step through using Debug, but you will not be able use Edit and Continue....that is an issue that you'd have to take up with Microsoft, no one can use edit & continue in a 64bit app. (The app in this case is Autocad, not your dll).
thanks for replying.
this is what i get. but somehow when step out it will to through the command method sub which is a different class file.
i set 4.0 yesterday after seeing that message right away but didn't make any difference. no edit is fine i am used to it already. but somehow on microsoft if you search debug x64 class library they said oh just change the cpu or something then should work. i guess not for autodesk .net stuff.
>> this is what i get
What I can imagine then (and you look into) is:
Just found: also Kean Walmsley has a blog in this: <<<here>>>
[EDIT] OK, Jeff is the faster one [/EDIT]
HTH, - alfred -
ok. apparently some old school dude is using windows xp 32bit and said my program doesn't work. got the following messages.
so what it takes to make this work for windows xp 32bit? i was thinking about .net 4.0 not installed but then when you install c3d 2012 it will install all those.
rename .doc to docx if can't see. interesting. using word 2010 but xp 32? lol.