pio!pio!

Just as a test, I downloaded the 3.2 source and opened in VS2008, it converted the project, and I built it both targeting .net 2.0 and .net 3.5 here are my notes: - the only real issue was that mt.exe does not like paths with spaces on it, even if encapsulated with quotation marks, so the project had to be in a path w/o spaces - there is a warning about wp64 being deprecated from cl.exe (there is a separate 64 bit compiler now?) - besides those, there were no build issues (cool!) - some of the assemblies that were built targeting .net 2.0 were smaller but not many...but i didn't diff the binaries of assemblies whose size was identical to see if it generated the same instructions. - some assemblies targeting .net 3.5 were larger... - i was able to run the program and play with it a little, not a full regression test, but interesting to see - i ran w/ /skipRepairAttempt on both debug and release mode as I didn't have the extra language strings and it couldnt rebuild them - the error message when executing the binary regarding /skipRepairAttempt mentions that you are running the debug version, even when running the release version (?!) comments: - i didn't run any performance tests, it felt just as snappy. - it was one of the easiest migrations of a project/solution i've ever had!

agreed!

Even still, it isn't worth downloading a huge framework (upgrading from 2.0 means about 120 mb, upgrading from 3.0 means 50 mb, and starting from scratch is about 200mb) for one or two plug-in's, besides, the new VS allows you to compile class libaries for .NET Frameowkr 2.0, 3.0 and 3.5, the only new features you'd need are in PDN itself, you wouldn't need any of the .NET Framework libaries, apart from the drawing tools which aren't needed for PDN 3.20 because of the IndirectUI system. at my job I did a test where I used VS2008 and compiled my solution targeting .net 2.0, the assemblies it generated were in total about 15% smaller than the ones that were generated from vs2005 I read in a programming blog that even if you target .net 2.0 in vs2008, it still uses the newer compiler, so you still get a benefit from all the lessons they learned and compiler optimizations from vs2005 to vs2008 while maintaining compatibilty. just food for thought

What about just compiling with Visual Studio 2008? The C# compiler is supposed to be improved compared to the one that shipped with older versions. The CLR in 3.0/3.5 is supposed to be better than the one in 2.0 too, right?