>Should I keep the target as .Net 1.1 (very old and not installed on all computers) or upgrade?
>If I upgrade-is it 2.0 Ens? Or upgrade to the latest 3.5 (our customers use Windows XP, Vista and Windows 7)
>If I target my application to 2.0 and the user has 3.5, what will happen? Should users install .Net 2.0 on .Net 3.5? Even if the old version is installed “above” the new version, can it work side by side? Or the application can run normally because 3.5 “includes” 2.0?
Thank you,
Atara
.. .
Thank you.
I think I will target 2.0 and cover me Most of the customers, if the customer has not installed any .Net, I will ask him to install the latest version (3.5 and higher version 4)
Can you confirm that .Net 3.5 just added more assemblies To 2.0, and does not include the bug fixes for the 2.0 assembly?
(My user’s computer skills are not high, the less installation the better)
… Update:
Look at my question –
Microsoft .NET compatibility
Thank you for your answer.
Atara
When positioning the framework, you need to consider one The thing is the impact on the customer. To use your application, the target customer also needs to install the corresponding .Net framework on their computer. The cost of doing this may vary, depending on the scenario. Best case Yes. Net framework has been installed, so users can install your application.
> 1.X: Pre-installed on W2K3
> 2.0: Pre-installed on Windows Vista, W2K8 and Win7< br>> 2.0SP1: Pre-installed on Win7 (maybe W2k8)
> 3.5: Win7 (maybe W2K8)
My personal choice is to use the 2.0 framework, unless your application is actually Use the features in the framework version 3.5 or higher. This increases the chance that the end user has already installed the .Net framework on their computer, thereby reducing the cost of installing the application.
For the last part, if the customer With a higher version of the .Net framework, then your application will work normally.
We are now using VS2003 (targeting .Net 1.1), and we want to upgrade to VS2008, but I want to know what the new .Net target should be?
>Should I keep the target as .Net 1.1 (very old and not installed on all computers) or upgrade?
>If I upgrade-is it 2.0 Ens? Or upgrade to the latest 3.5 (our customers use Windows XP, Vista and Windows 7)
>If I target my application to 2.0 and the user has 3.5, what will happen? Should users install .Net 2.0 on .Net 3.5? Even if the old version is installed “above” the new version, can it work side by side? Or the application can run normally because 3.5 “includes” 2.0?
Thank you,
Atara
.. .
Thank you.
I think I will target 2.0 and cover me Most of the customers, if the customer has not installed any .Net, I will ask him to install the latest version (3.5 and higher version 4)
Can you confirm that .Net 3.5 just added more assemblies To 2.0, and does not include the bug fixes for the 2.0 assembly?
(My user’s computer skills are not high, the less installation the better)
… Update:
Look at my question –
Microsoft .NET compatibility
Thank you for your answer.
Atara
Quickly explain, if you upgrade to VS2008, you can’t Positioning any 1.X framework. VS2008 only supports positioning 2.0, 3.0 and 3.5 frameworks.
When positioning frameworks, one thing you need to consider is the impact on customers. To use your For applications, target customers also need to install the corresponding .Net framework on their computers. The cost of doing this may vary, depending on the scenario. The best case is that the .Net framework is already installed, so users can install you Application.
> 1.X: Pre-installed on W2K3
> 2.0: Pre-installed on Windows Vista, W2K8 and Win7
> 2.0SP1: Pre-installed on Win7 ( May be W2k8)
> 3.5: Win7 (maybe W2K8)
My personal choice is to use the 2.0 framework, unless your application actually uses the features in the 3.5 or higher framework. This It increases the chance that the end user has already installed the .Net framework on their computer, thereby reducing the cost of installing the application.
For the last part, if the customer has a higher version of the .Net framework, then your The application will work normally.