|
Hello everyone,
My C# application is built for "Any CPU" option using .Net framework 2.0 using Visual Studio 2008, and I run it on a machine which is Winsows Server 2003, x64. I installed,
- .Net Framework 32-bit version 2, 3, and 3.5;
- .Net Framework 64-bit version 2, 3, and 3.5.
My question is, when run the application on the specific machine, which version of .Net Framework will be used? And why (what is the rule to choose)?
thanks in advance,
George
|
|
|
|
|
The framework depends on the OS that is on the server.So if there is X64 OS then framework would be 64 bit and same will be used by the application
Cheers!!
Brij
|
|
|
|
|
|
I believe 64 bit framework will be used if you are on a 64 bit machine. I am not sure though.
|
|
|
|
|
Thanks N a v a n e e t h,
The machine run the code is server 2003 (x64) and the build machine make the binary "Any CPU", not specifying x64 in build option, and when making the build version 2.0 CLR is used.
1.
In this situation, you mean 64-bit framework is always used?
2.
Which version of CLR is used on the machine? 2.0? 3.0 or 3.5?
regards,
George
|
|
|
|
|
if you are system is Win2k3 , X64 your .NET will used only 64 bit version of Framework.
if you want to run the application on x64 bit system its need .NET Framework 64 bit OS , but i think it will not run on 32 Bit System.
|
|
|
|
|
|
If you are running on a 64-bit OS and are compiled under the "Any CPU" option it should choose the 64-bit Fx if available. Since you specifically said you compiled targeting the Fx 2.0 your application will run against that version by default unless it is a Windows service, in which case it will run against the latest version of the Fx that is installed.
Scott Dorman Microsoft® MVP - Visual C# | MCPD
President - Tampa Bay IASA
[ Blog][ Articles][ Forum Guidelines]
Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai
|
|
|
|
|
Hi Scott,
Sorry it is a Windows service -- so it will run under CLR 3.5? 
How to check which version of CLR a process is using?
regards,
George
|
|
|
|
|
Yes, a windows service will, by default, run using the latest available Fx version (in this case Fx 3.5) [A minor correction, the CLR version from Fx 2.0 on is still CLR version 2.0.]
From inside the process you can access the Environment.Version[^], which will return the version number of the CLR you are running under (not the Framework).
Scott Dorman Microsoft® MVP - Visual C# | MCPD
President - Tampa Bay IASA
[ Blog][ Articles][ Forum Guidelines]
Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai
|
|
|
|
|
Scott Dorman wrote: Yes, a windows service will, by default, run using the latest available Fx version
This is a new info for me. Even the service is targeted to framework 2.0, it takes the latest version ? Is there any documents to prove this ?
|
|
|
|
|
I am also asking this.
regards,
George
|
|
|
|
|
I haven't been able to find the documentation I saw this in, but it has to do with the way certain unmanaged applications (like IIS, SQL, DLLHost, etc.) actually host an instance of the .NET runtime. I'm still looking, so if I find the information I'll update the post.
Scott Dorman Microsoft® MVP - Visual C# | MCPD
President - Tampa Bay IASA
[ Blog][ Articles][ Forum Guidelines]
Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai
|
|
|
|
|
Thanks Scott,
1. If in my process, I have not added any code to retrieve Environment.Version, how could I retrieve the CLR version it is using?
2. "A minor correction, the CLR version from Fx 2.0 on is still CLR version 2.0." -- I am confused. Sorry English is not my native language, do you mean .Net Framework 2.0 and CLR 2.0 are the same thing?
regards,
George
|
|
|
|
|
1 - You have to add and re-deploy your application.
George_George wrote: .Net Framework 2.0 and CLR 2.0 are the same thing?
They are not the same. One is a set of classes and other one is "Common language runtime". He meant .NET Framework 3.5 uses CLR version 2.0.
|
|
|
|
|
Thanks N a v a n e e t h,
1.
So, no way to know which CLR version is used from outsire?
2.
Have you found any documents saying Windows Service will always use latest CLR version other than the CLR version used to build it?
3.
N a v a n e e t h wrote: .NET Framework 3.5 uses CLR version 2.0
-- confused about this, you mean for the common parts between 2.0 and 3.5, like System.XXX and Net.XXX classes, they share the same binary code?
regards,
George
|
|
|
|
|
George_George wrote: Have you found any documents saying Windows Service will always use latest CLR version other than the CLR version used to build it?
I haven't been able to find the documentation I saw this in, but it has to do with the way certain unmanaged applications (like IIS, SQL, DLLHost, etc.) actually host an instance of the .NET runtime. I'm still looking, so if I find the information I'll update the post.
George_George wrote: So, no way to know which CLR version is used from outsire?
Not really, no. You could use a tool like ILDasm to inspect the PE header and manifest metadata, which will tell you what version of the CLR the binary was compiled against, but that isn't really going to tell you what version you may be running on. Are you asking because you are running in to a problem or is this just a "want to know" type of question? If you're running in to a problem, posting what that problem is may help get you the right information to resolve it.
George_George wrote: confused about this, you mean for the common parts between 2.0 and 3.5, like System.XXX and Net.XXX classes, they share the same binary code?
The thing to keep in mind here is that NetFx v3.0 and NetFx v3.5 are really a set of framework libraries (WPF, WCF, WF, Linq, etc.) that extend the runtime engine (the CLR) which is CLR v2.0. (This simplifies things a bit, since there are actually service packs that are distributed as part of NetFx 3.0 and 3.5 that are mandatory and irreversible once installed.)
Scott Dorman Microsoft® MVP - Visual C# | MCPD
President - Tampa Bay IASA
[ Blog][ Articles][ Forum Guidelines]
Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai
|
|
|
|
|
Thanks Scott,
Scott Dorman wrote: The thing to keep in mind here is that NetFx v3.0 and NetFx v3.5 are really a set of framework libraries (WPF, WCF, WF, Linq, etc.) that extend the runtime engine (the CLR) which is CLR v2.0. (This simplifies things a bit, since there are actually service packs that are distributed as part of NetFx 3.0 and 3.5 that are mandatory and irreversible once installed.)
So, for the common parts of library, like System, string, sockets and http related classes, they are common in 2.0/3.0/3.5 correct?
regards,
George
|
|
|
|
|
George,
There has always been some level of confusion regarding the differences between Framework (Fx) versions, CLR versions, and language versions. Here is a brief explanation up through VS2008 (.NET Fx 3.5): http://geekswithblogs.net/sdorman/archive/2007/06/12/Visual-Studio-2008.aspx[^]
As for retrieving the CLR version your process is using from inside your process the only real option is to add a call to Environment.Version.
Scott Dorman Microsoft® MVP - Visual C# | MCPD
President - Tampa Bay IASA
[ Blog][ Articles][ Forum Guidelines]
Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai
|
|
|
|
|
Thanks Scott,
1.
From document you referred, I learned .Net Framework is the library, and CLR is used only for the runtime engine, manages the libraries, correct understanding?
2.
Do you have any document mentions for Windows Services, the lastest version .Net Framework other than the version used to make the build is used please?
regards,
George
|
|
|
|
|
George_George wrote: manages the libraries
.NET framework is a collection of classes, ofcourse a library. Common language runtime is the runtime where these libraries are executed.
|
|
|
|
|
Thanks N a v a n e e t h!
A further question -- "Do you have any document mentions for Windows Services, the lastest version .Net Framework other than the version used to make the build is used please?" 
regards,
George
|
|
|
|
|
My problem is:
I have 3 main classes A, B and C (B and C are derivated from A)
I have a generic class F
And I have derivated F to work with B and C:
class FB : F<B>
class FC : F<C>
Now, in my main application I have a method that should work with FB and FC (also with any F<> that uses a A derivated type as parameter)
I tried to do this, but it doesn't compile:
void WorkWithData(F<A> data) {}
FB testB = new FB();
FC testC = new FC();
WorkWithData(FB);
WorkWithData(FC);
Is there anyway to fix it?
Thanks,
Dirso
|
|
|
|
|
With the current state of C# (and VB), that sort of thing is not possible. Apparently the CLR supports this sort of assignment (known as covariance and contravariance), but the C# and VB language teams decided not to implement it yet.
A decent series of blog posts that talk about the topic can be found here [^]
|
|
|
|
|
A suggested, have a google for covariance and contravariance. This is supported in some cases, if the type parameter is used in a read-only manner. IEnumerable<t> can be used covariantly, IList<t> can't.
You can make it work by declaring your method as:
void WorkWithData<t>(F<t> data) where T : A { ... }
The compiler may infer the appropriate specialization of WorkWithData for you. If not you'll have to call it like WorkWithData(testB);
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
