TheSwamp
Code Red => .NET => Topic started by: Glenn R on April 02, 2006, 07:18:32 PM
-
Well, I put Vanilla 2007 onto the machine and configured it so it's working to my liking.
So, I then jump into VS2005, copy my old solution which contains about 20 projects and open it up. VS2005 asks to convert it and it does with no errors.
I then change all the references from Acad2006 to Acad2007 (acmgd.dll etc.) and then compile. No errors! Woohoo! Start debug and acad flashes up then disappears - it errors with wrong imagefileformat or something of the like. I then look at the properties of the newly attached 2007 references and VS2005 is thinking they're the 2006 ones according to the 'Path' property!?!
Has anybody had this happen to them or even heard of it?
Cheers,
Glenn.
-
Haven't tried to use the 2007 assemblies yet, so Nope, not yet.
-
Found it. Changed the property 'Specific Version' to true.
-
Found it. Changed the property 'Specific Version' to true.
I noticed the same thing the other day on a project, but didn't have time to research it. Thanks for positing the fix Glenn!
I had another existing project reference the new 2007 assemblies just fine. Any idea of why some projects have issues? The only difference that I can immediately remember between the two projects that I've converted are that the one that had trouble with was started with references to the 2005 assemblies and the other was started with 2006. That's just me thinking out loud of course. I'm going to hit MSDN when I get some free time.
Free time...bwa haha ha ha aah...I crack myself up sometimes :)
-
Bobby,
I noticed the following when going thru this:
When in the References dialog -> .NET Tab, in vs2005, it shows the Acad2006 libraries but does NOT show the 2007 libraries.
I can only guesstimate that VS2005 is a bit smarter in finding .NET libraries than vs2003 and the 2007 libraries aren't registered or some such...just a guess.
Cheers,
Glenn.