This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Snoopstah
Level 7
‎Jan 15, 2009 11:48 PM

[System] vs [CommonFiles]

I have read much conflicting information on this and I am hoping someone can set me straight.

Our product currently deploys several files to the System32 directory which I believe is a bad thing. They are not .Net resource files.

If they are deployed directly to system32 then all is working.

If I deploy these to [CommonFiles]\Some Folder\, I then need to add that to System Environment Variable PATH. This seems quite tedious.

Which is the correct way to deploy these resource files?

eg: They are potentially shared ocx / resource files such as DynaZIP.
Labels (1)
Labels
0 Kudos
(2) Replies
MEinstaller
Level 7
‎Feb 25, 2009 07:20 AM

I am doing the same thing in one of my projects right now because I believed that having dlls in the system32 was a bad idea. I have placed the dlls in another directory and I am now adding to the path. I am running into a problem registering some dlls because these shared dlls are not being picked up right away from the path, just something to be aware of.
0 Kudos
MGarrett
Level 6
‎Feb 25, 2009 12:02 PM

If you modify the environment PATH, unfortunately the new PATH doesn't take effect until the computer is rebooted.
0 Kudos