I just wanted to check that this rumor of no multi-targeting in Express 2008 wasn't true as I'm looking in to possibly switching up to using Visual C# Express 2008 Beta 2 for working on my WPF app now that the designers seem a lot more stable and the whole
IDE a lot faster.
Will multi-targeting remain in the express editions in the RTM version? I'm currently pointing my program at just .net 3 rather than 3.5 as I don't want to push too much extra download on to my XP users in one go.
Can someone confirm the features are staying in the free versions of Visual Studio? ![]()
-
-
The rumor is not true.
-
Nidonocu wrote:Will multi-targeting remain in the express editions in the RTM version? I'm currently pointing my program at just .net 3 rather than 3.5 as I don't want to push too much extra download on to my XP users in one go.
.NET3.5 is a new CLR and BCL version (woo & yay & hoopla for LINQ), .NET3.0, as you should know, is just those W*F libraries, it's all marketing, so if you're targeting .NET3 you're actually targeting .NET2
EDIT: Unless you already knew that, in which case I sound like patronising bastárd. My apologies.
-
-
-
W3bbo wrote:
Hides the new libraries in .Net 3.0 from Intellisense, I assume (too lazy to check).
Nevertheless, the options there, so it probably does something
-
Well if you target v3.5 of the framework it will require users to have 3.5 installed regardless if you use the new features or not. So if you don't want to require your users to install v3.5, you select 3.0.
-
W3bbo wrote:.NET3.5 is a new CLR and BCL version (woo & yay & hoopla for LINQ), .NET3.0, as you should know, is just those W*F libraries, it's all marketing, so if you're targeting .NET3 you're actually targeting .NET2
Incorrect, 3.5 like 3.0 uses the 2.0 CLR. -
Thanks for the replies, though I did know which CLR's worked on what versions.

Is this a known issue by the way or just me?
When I try to run some of the tools:
C:\Program Files\Microsoft Visual Studio 9.0\SDK\v3.5\Bin>sgenUnhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'sgen, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed. (Exception from HRESULT:0x8013141A)
File name: 'sgen, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' ---> System.Security.SecurityException: Strong name validation failed. (Exception from HRESULT: 0x8013141A)
The Zone of the assembly that failed was:
MyComputer -
dahat wrote:

W3bbo wrote:
.NET3.5 is a new CLR and BCL version (woo & yay & hoopla for LINQ), .NET3.0, as you should know, is just those W*F libraries, it's all marketing, so if you're targeting .NET3 you're actually targeting .NET2
Incorrect, 3.5 like 3.0 uses the 2.0 CLR.
Someone should create a version matrix.
Is this right then?.NET BCL CLR Compilers 1.0 1.0 1.0 1.0 1.1 1.1 1.1 1.1 2.0 2.0 2.0 2.0 3.0 2.0 2.0 2.0 3.5 3.0 2.0 3.0 -
CannotResolveSymbol wrote:From Visual C# EE 2008 Beta 2:
Except the OP is asking about *Express*
And there is no Express public beta right now is there?
Fankly it wouldn't surprise me if there was no multi-targetting, it's not really a hobby developer feature.
-
W3bbo wrote:

dahat wrote:

W3bbo wrote:
.NET3.5 is a new CLR and BCL version (woo & yay & hoopla for LINQ), .NET3.0, as you should know, is just those W*F libraries, it's all marketing, so if you're targeting .NET3 you're actually targeting .NET2
Incorrect, 3.5 like 3.0 uses the 2.0 CLR.
Someone should create a version matrix.
Is this right then?.NET BCL CLR Compilers 1.0 1.0 1.0 1.0 1.1 1.1 1.1 1.1 2.0 2.0 2.0 2.0 3.0 2.0 2.0 2.0 3.5 3.0 2.0 3.0
I think this is closer:
... although I don't have a machine handy that I can check and am not 100% sure if there were any compiler changes with 3.0... however fully expect there were enough to rev the #..NET BCL CLR Compilers 1.0 1.0 1.0 1.0 1.1 1.1 1.1 1.1 2.0 2.0 2.0 2.0 3.0 3.0 2.0 3.0 3.5 3.5 2.0 3.5 -
blowdart wrote:
And there is no Express public beta right now is there?
Um, yes, there is.
Haven't tried it to confirm/deny though. -
AndyC wrote:

blowdart wrote:
And there is no Express public beta right now is there?
Um, yes, there is.
Haven't tried it to confirm/deny though.
Oh cool; must admit I'd never kept an eye on express.
-
blowdart wrote:
Oh cool; must admit I'd never kept an eye on express.
No, normally I wouldn't either, but we're looking into running an XNA Express based course (including a lab full of 360s) so I've been paying slightly more attention than usual.
-
AndyC wrote:

blowdart wrote:
Oh cool; must admit I'd never kept an eye on express.
No, normally I wouldn't either, but we're looking into running an XNA Express based course (including a lab full of 360s) so I've been paying slightly more attention than usual.
I doubt work would let me get that from my training budget
You going to speak on it at DDD5?
-
dahat wrote:

W3bbo wrote:

dahat wrote:

W3bbo wrote:
.NET3.5 is a new CLR and BCL version (woo & yay & hoopla for LINQ), .NET3.0, as you should know, is just those W*F libraries, it's all marketing, so if you're targeting .NET3 you're actually targeting .NET2
Incorrect, 3.5 like 3.0 uses the 2.0 CLR.
Someone should create a version matrix.
Is this right then?.NET BCL CLR Compilers 1.0 1.0 1.0 1.0 1.1 1.1 1.1 1.1 2.0 2.0 2.0 2.0 3.0 2.0 2.0 2.0 3.5 3.0 2.0 3.0
I think this is closer:
... although I don't have a machine handy that I can check and am not 100% sure if there were any compiler changes with 3.0... however fully expect there were enough to rev the #..NET BCL CLR Compilers 1.0 1.0 1.0 1.0 1.1 1.1 1.1 1.1 2.0 2.0 2.0 2.0 3.0 3.0 2.0 3.0 3.5 3.5 2.0 3.5
Yea, the fact that you can run .net 2.0 and 3.0 and 3.5 applications in the same App Pool in IIS points to additions, not changes

Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.