Learn how to a build a cloud-first strategyRegister Now

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

Windows Compatibility Issues

I recently wrote a program in XP, switching between Pro and Media Center Edition.  The other day, I attempted to install the program onto a Windows 2000 32 bit machine and it failed; the program also crashed in Vista.  I'm new to the compatibility in code thing, but I was hoping that there could be some reference I could just add to my program and everything would work, but I'm probably wrong.  So my question is, what is the easiest way to resolve compatibility issues with Windows in C#, or is there not an easy way to do it?
0
jason4659
Asked:
jason4659
  • 5
  • 5
1 Solution
 
Anurag ThakurCommented:
as far as i know if i write an application with C# on XP (any version) it should run with any other 32 bit microsoft operating system unless and untill you are using an 3rd party component which is specifically designed to be used with XP

why your program is not running on Vista and 2003 server because both these operating systems have tight security and does not allow some applications to run
in vista there is user access control and in the server there are other settings which might be required

be more specific with your question we might be able to help with better solutions
0
 
jason4659Author Commented:
UAC has been disabled in Vista, and it's Windows 2000, not 2003 Server.  What kind of specifics do you need to better answer the question?
0
 
Anurag ThakurCommented:
see the only reason if you have developed a pure .net application not working on a 2000 server or vista is because of security because i am running my applications on all the servers and on vista also so there is no compatibility issue
initially it was a UAC issue on vista but after disabling it its working fine and on servers there is always some kind of setting required to make it work

for modifications on serves you need to know what all you are using in your application and what all are restricted by the server which you might have to enable

regarding what you want to share with us about your application is up to you - it will be better to know if you are using any kind of third party components or any other introp components etc
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
jason4659Author Commented:
"it will be better to know if you are using any kind of third party components or any other introp components etc"

I'm using system.runtime.interopservices, does that make a difference?
0
 
jason4659Author Commented:
I'm also using System.Management.
0
 
Anurag ThakurCommented:
if you are using system.runtime.interopservices i am assuming here that you are using some com component and its introp assembly
if the com component is not registered you are going to get an error

resgister the com component and then try again
0
 
jason4659Author Commented:
I can't register the com component because I'm using a Windows Application, and that option isn't available...
0
 
Anurag ThakurCommented:
windows dosent stop you from registering the com component
moreover its the part of the setup process to register the com pomponents if any
0
 
jason4659Author Commented:
Do you know how to go about registering the com component?
0
 
Anurag ThakurCommented:
regsvr32 command on the command prompt does that
http://support.microsoft.com/kb/249873
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

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