Why is no .net 2.0 version?

Dec 11, 2009 at 3:23 PM

Why do I need .net 3.5 with the latest version? Any chance to change it that we have both versions again?

Coordinator
Dec 11, 2009 at 4:26 PM

Sorry, I decide to move to only support .net 3.5.

I heard we can just deploy the assemblies of Linq to our bin folder to make it run on .net framework 2.0.

But it needs to use visual studio 2008 for develop at least, doesn't support visual studio 2005 anymore.

Change set 62160 is the last change set which supports .net 2.0.

Dec 11, 2009 at 9:59 PM

I'm already using VS2008, too bad that I still have some Win2k PCs where my app has to run till 2010 where support for Win2k ends by MS. And Win2k is .net 2.0 only.

Coordinator
Dec 12, 2009 at 6:19 AM

The reason of .net 3.5 doesn’t support win2k:

The main reason that .NET Framework 3.5 is not supported on Windows 2000 is due to the fact that .NET Framework 3.0 is not supported on that platform.  While some of the functionality of .NET Framework 3.5 will work on windows 2000, the components dependent on 3.0 will not, becuase they were not designed to work on Windows 2000.

Windows 2003 Server is a supported platform and works just fine.

.NET Framework 3.5 = .NET Framework 3.0 SP1 + linq + new wpf + new wcf, etc.

DbEntry.Net just need Linq, so I think deploy the linq assemblies should work for win2k.

There are some articles talk about this:

http://www.manning-sandbox.com/thread.jspa?threadID=20295

http://channel9.msdn.com/forums/TechOff/254146-Linq-Sample-of-the-Week-Part-2-Linq-in-NET-20/

Dec 15, 2009 at 1:59 AM

ok, I got it working. Adding the reference doesn't work the offical way. After adding the reference to System.Core.dll, I had to unload the project and chance the required .net version for System.Core.dll from 3.5 to 2.0. After reloading the project I was able to compile it.

The confusing part is now, that the System.Core.dll is never used. Only the reference in VS2008 is needed.

Coordinator
Dec 15, 2009 at 2:51 AM

Glad you made it work.

What I think is you might could just use .net 3.5 to develop and copy System.Core.dll to your bin folder on the working machines. Never test it but I guess it might work.

Use Linq is better when you re-define the name with DbTable/DbColumn. And it has compile time check and intellisense.

Dec 15, 2009 at 1:26 PM

The System.Core.dll is never needed. I didnt copied it to the Win2000 VM and my app still works. And I've used the functions which required the reference to System.Core.dll, but everything works fine. So unless you use Linq, the only the reference is needed and this is ok for me.