[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1097
  • Last Modified:

Windows XP Required for .NET Applications?

Hi guys and gals,

I've packaged a VB6 app in a Windows Forms project, so that I can use ClickOnce to deploy it and install updates for me.  On WinXP, everything works fine, but when I try to run the app installer on Windows 2000 Professional, I get the message "Unable to install or run this application. This application requires your system to be updated to Microsoft Windows Operating System version 5.1.2600.00."

I was under the impression that the minimum requirements for .NET apps were the same as for the .NET Framework 2.0, which clearly includes Win2K.

Anyone know why I can't install this little app on Win2K Pro?

TIA!

Steve
0
seadriver
Asked:
seadriver
  • 6
  • 4
1 Solution
 
surajgupthaCommented:
Check your assembly manifest. It contains a minimum version number requirement. Just make it less so the install may proceed

  <dependency>
    <dependentOS>
      <osVersionInfo>
        <os majorVersion="5" minorVersion="1" buildNumber="2600"
servicePackMajor="0" />
      </osVersionInfo>
    </dependentOS>
  </dependency>
0
 
surajgupthaCommented:
Windows 2000 has a Version number: NT 5.0.2195. And you assembly manifest may have a 2600 minimum by default.
0
 
seadriverAuthor Commented:
Thanks for that very quick reply.

There doesn't seem to be any way to alter the minimum required OS in Visual Studio 2005, and I can't just edit the manifest because it's signed, and the changes will invalidate it.  I tried copying the code block into my app.manifest file, but my entry was overwritten in the build.  Went back to 5.1.2600.00.

So... I have to create a console exe to edit the manifest, then run it as a post-build event?

Can you use mage to alter a manifest, or just to create one?

Thanks again for your help.  You guys are life savers!

Steve
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
surajgupthaCommented:
In the first place, In the contents of your application manifest do you see a XML block similar to the one i have pasted?
0
 
seadriverAuthor Commented:
Yes.

I copied and pasted it into my app.manifest file, then modified it to set the minimum version to 4.0.0.0.

However, when I build the project, VS2005 overwrites my code block with it's own, setting the min version back to 5.1.2600.00.

As I said, I can't find any configuration options for minimum OS in VS2005, and I can't edit the manifest after it's been created, because my changes invalidate the file signature key.
0
 
surajgupthaCommented:
>> However, when I build the project, VS2005 overwrites my code block with it's own, setting the min version back to 5.1.2600.00.

Does your project update the manifest everytime it is built?
0
 
surajgupthaCommented:
Try updating your manifest manually and try signing it from mage and not from VS2005.
0
 
seadriverAuthor Commented:
Thanks, I finally got it working, using mage to sign the files.

After changing the application manifest, you have to remember to re-reference the application manifest from the deployment manifest.  Otherwise, you get the "Reference in the deployment does not match the identity defined in the application manifest" error.

Thanks for all your help.

Steve
0
 
seadriverAuthor Commented:
For the benefit of anyone who might have the same problem, here's the right way to do this:

 http://msdn2.microsoft.com/en-us/library/ke5z92ks(VS.80).aspx

Since the setting is changed in a post-build event, prior to publishing, the manifests don't need to be re-signed in mage.
0
 
surajgupthaCommented:
Cool. I didnt know it could be done this way too. Thanks...
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now