cr113
12/6/2009 8:11:00 PM
On Dec 2, 12:48 pm, "Wilson, Phil" <ph...@wonderware.nospam.com>
wrote:
> Exactly what are you worried about here? Your original post was about
> installing the .NET Framework, and that creates registry entries as well as
> install the support framework for managed code. If these military computers
> are never going to run any managed code then you should not have gone down
> the .NET path in the first place. However your follow-up question is about
> registering your Dlls. Sometimes people use that word in a COM sense, other
> times meaning ":nstall into the GAC", so it would help to be a bit more
> precise about what your Dlls do. So what is the issue? Is it your Dlls?
> Installing the .NET framework? Both? And do you or the military believe that
> installing the .NET Framework (or registering your Dlls) will screw up the
> OS?
Damn. I'm back to VB.NET. I tried Access, didn't like it. I tried
Excel, it was better but it still has issues.
Question. I still don't want to copy any files to common folders such
as Windows/System32 and I don't want to write to the registry. As long
as they have the proper Framework installed I should be OK, right?
What I'm thinking is I can get them to install the framework if they
don't have it. That limits my liability. What's the most "graceful"
way to check to see what framework they have installed? Can I get
my .NET exe to check first for the framework version to make sure it
can run?