thanks for the suggestion on app path. I had looked into that, but unfortunately, the app path is not search when commands are run from the command line. only from the run window. mike c

I have a setup project and I set one of the files's Exclude property to true in the File System screen. Once I did this, the file no longer appears in the screen (but it is still part of the installation). I now need to remove the file, but cannot figure out how, because I can't see it! Does anyone know how I can view and remove files set to Exlclude in the File System screen? thanks... mike c

Yes. Thus far, I have sent it to three people, and it didn't work for any of them. They all have the same version of the flash player also. mike c

I am building a simple test application in c# that uses the Flash player ActiveX control to display some data. I have two Classes in c#: FooWindow.cs Foo.cs I then embed the Flash player in my app in visual studio. When I compile everything, it creates the following files: AxInterop.ShockwaveFlashObjects.dll Interop.ShockwaveFlashObjects.dll stdole.dll Foo.dll FooWindow.exe This all works perfectly on my machine, but when I send it to other people to test, they get various errors. I am sending all of the files. Do I have to do anything special to distribute an app which uses an ActiveX control? Thanks for any input... mike c

Thanks for the info. This is actually exactly how I have my solution set up, and as you point out, it creates multiple dlls and and EXE. I was trying to find a way to then include all of those in one file, so I don't have to distribute all of the DLLs seperately. thanks again for the suggestions... mike c

I have been thinking about this. So i could just combine all of the DLLs into one DLL? i.e. I would have one exe and one dll? The DLL would then load the EXE. Would I have to change anything in the EXE or would it know to look in the new DLL? thanks for the input. I am new to c# and thus am not familiar with how apps are usually deployed. mike c

>Why not make one big assembly in the first place? Because my code is broken up into different projects to make it more reusable. I guess i could make one project that linked to all of the other individual files, but I just figured there would be another way to do it. I have been rpetty surprised by how difficult this has been, and how little information i can find on it. Thanks for the info... mike c

Ok. After about 12 hours of trying to combine multiple assemblies into a single EXE, I am finally making some progress. I ended up compiling each class into its own module (quite a pain). I am now trying to use al.exe to combine all of them. If I use the following command line: al.exe ActionNotSpecifiedException.netmodule Arguments.netmodule ConsoleLogger.netmodule DirectoryUtils.netmodule FileLogger.netmodule FileUtils.netmodule ProgCommand.netmodule ProgInfo.netmodule ProgNotFoundException.netmodule InvalidCommandLineException.netmodule Logger.netmodule LoggerArrayList.netmodule LoggerManager.netmodule StreamWriterLogger.netmodule StringArrayList.netmodule TextWriterLogger.netmodule TimeOutException.netmodule ProgCommandRunner.netmodule /main:mesh.Prog.ProgCommandRunner.Main /out:ProgCommand.exe /target:exe I can actually create the ProgCommand.exe executable. Except that it has to be in the same directory as the modules in order to run. So close, yet so far. I also tried to combine everything in my make file with the following code: $(DEST)\$(ASSEMBLY): $(METADATA) $(MODULES) $(DEST) $(CSC) $(EXETARGET) /addmodule:$(MODULES: =;) /main:mesh.Prog.ProgCommandRunner.Main /out:$@ %s which on the command line translates to: csc /nologo /debug+ /d:DEBUG /d:TRACE /t:exe /addmodule:.\Arguments.netmodule;.\InvalidCommandLineException.netmodule;.\DirectoryUtils.netmodule;.\FileU tils.netmodule;.\TimeOutException.netmodule;.\StringArrayList.netmodule;.\Logger.netmodule;.\LoggerArrayList.netmodule;.\TextWriterLogger.netmodule;.\ConsoleLog ger.netmodule;.\StreamWriterLogger.netmodule;.\FileLogger.netmodule;.\LoggerManager.netmodule;.\ActionNotSpecifiedException.netmodule;.\ProgCommand.netmodule;. \ProgNotFoundException.netmodule;.\ProgInfo.netmodule;.\ProgCommandRunner.netmodule /main:mesh.Prog.ProgCommandRunner.Main /out:.\ProgComma nd.exe ..\build\AssemblyInfo.cs However, this gives me the following error: error CS1555: Could not find 'mesh.Prog.ProgCommandRunner.Main' specified for Main method NMAKE : fatal error U1077: 'csc' : return code '0x1' Does anyone have any idea what I am doing wrong? I have been trying to get this to work for quite some time. All I want to do is combine multilple projects into one executable. Thanks in advance... (I hope)... mike c

thanks. It is not there, so perhaps I installed the wrong sdk. I realized that I can have the installer launch an executable or call a dll (written in c#?). So, i might just put the code I need in there. mike c

Thanks for the tip. So, I would basically create some seperate code (in c#?) which would manipulate the environment variables using the Environment Table. Basically, I want to add my application install directory to the path during installation, and remove it if the app is uninstalled. Btw, I jsut download and installed the SDK you mention above, but I cant seem to find the orca tool you referenced. thanks for the leads... mike c

I am creating a msi installer for a command line program I have written in c#. I would like the user to be able to just type the program name from anywhere on the file system, and have the program run. Basically, I need to alter the PATH environment variable to include the installation directory. I have spent some time looking for solutions, and I haven't been able to find any thing definitive. Options I have found include: -Editing the registry from the installer: requires reboot, and deletes entire path variable on uninstall. -calling a Custom Action DLL to edit the path. DLL must be written in c++ (is that correct?). Can't uninstall? -write a vbs script to be run by the installer and set the path. (I don't know VBS script) -provide instructions to the user to tell them how to edit their path : not very user friendly. However, none of these seem like good options. I understand some of the reasons why setting an environment variable is not really a good idea, but surely this is something that needs to be done quite often. So, any suggestions or ideas? mike c