mskeel said:The only way I would not go with the bootstrapper is if I didn't want my program installed if the target machine didn't have the .Net Framework.
mskeel said:And %WINDIR% is the environment variable you need to check. Go to a command prompt and hit 'set'. You'll see that variable toward the bottom.
JDYoder said:This is our scenerio, which is why I'm doing it this way. The long story is we are piggy-backing a very small .NET program onto a large VB6 program and setup that already exists. The .NET program is optional for the user. So I just need to check for the existence of the .NET framework and tell them if they don't have it.
But that's just for my machine. I need this to work on any machine, regardless if they have "C:\Windows", "C:\WINNT", "D:\BobsWindows", etc. So I'm assuming it's a registry call. But no one knows it?
You can find environment settings in the registry, though I am unsure where. And again, you can also check the environement variable directly. In .Net you would do this with a call to Environment.GetEnvironmentVariable(string)Quote:
Originally Posted by mskeel
And %WINDIR% is the environment variable you need to check. Go to a command prompt and hit 'set'. You'll see that variable toward the bottom.
But that's just for my machine. I need this to work on any machine, regardless if they have "C:\Windows", "C:\WINNT", "D:\BobsWindows", etc. So I'm assuming it's a registry call. But no one knows it?
PlausiblyDamp said:%WinDir% is a standard environment variable - you won't need to process the registry to find it. Just about every programming language / install tool has some method for evaluating these - what tool(s) are you looking at using to discover the existance (or not) of this directory?
pas30339 said:This should do the trick.
http://support.microsoft.com/default.aspx?scid=kb;en-us;315291