Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Ken Levy - In the field in Switzerland
Jan 09, 2006 at 5:24 PMI could be wrong (I live in the USA) but it would seem to me that a large part of the increase in price would be the VAT. Tax levels on software are nowhere near those levels in the states.
David Smith (and others) - Meeting the Interns
Aug 22, 2005 at 6:15 PMIll second that. I’ve used OneNote all year in school and am extremely happy with it. There’s no other program that I know about that comes anywhere near matching its capabilities.
Emily Rimas - Tablet PC Education Pack revealed
Aug 21, 2005 at 8:55 PM"Kids today have so many advantages I never had. There's no telling what I could've accomplished with a home computer and a handgun." — LeMel Hebert-Williams.
From:http://www.gdargaud.net/Humor/QuotesComputer.html
Emily Rimas - Tablet PC Education Pack revealed
Aug 17, 2005 at 9:45 AMCool.
You need any beta testers?
Emily Rimas - Tablet PC Education Pack revealed
Aug 16, 2005 at 10:25 PMJesse Kaplan -- Will your .NET 1.1 apps work on 2.0 or vice versa?
Jun 01, 2005 at 6:16 PMHummm. I guess your right, so that would instantly make it impossible to use a 2.0 component with a 1.1 program, unless it was on a 2.0 only system, or there’s a way to tell the framework to load the newest version (maybe an app.config setting?)
Jesse Kaplan -- Will your .NET 1.1 apps work on 2.0 or vice versa?
Jun 01, 2005 at 2:48 PMWhat happens if a program makes a call to a .net DLL that was complied on version 1.1 form 2.0? Does the DLL run in 1.1 or 2.0, and dose it matter if it’s a compile type reference or late binding?
Amanda Silver - Talking about Mort
May 26, 2005 at 3:31 AMAmanda Silver - Talking about Mort
May 26, 2005 at 3:20 AMMartin Taylor and Bill Hilf - Linux at Microsoft, Part II
May 04, 2005 at 6:12 PMFirst, windows with .net dose support side by side execution with assemblies of different version but the same name. If you have .net installed on windows go to C:\Windows\assembly and you’ll see that it’s not a ‘real’ windows directory as it has (probably) has files with the same name but different versions. It doses this via strong .net names witch not only allow many versions but provide assurance via public/private key pairs that your using the correct version of the assembly.
Also Buzza is correct, you can do the same thing with MSI, and if you’re distributing your app to any large number of users you probably should. But most of the time you can afford to just put all of the required dlls in your appdir and avoid the whole thing.
See more comments…