01-20-2006 05:34 AM
01-21-2006 07:52 PM
I think you will find it is number two.
Colin
01-23-2006 09:41 AM
What this means is that when you add a MSM to your vdproj deployment project, it will automatically add all dependent MSMs for you, this is the case in most MSI enabled setup tools. The file versioning issue means that an older file will never overwrite a newer file (if it is versioned which assemblies are by default). And the reference counting means that if someone else installs an application using MStudio's assemblies, when that application gets uninstalled it will not remove your dependencies because the MSI system on the deployment machine is reference counting what needs to be uninstalled.
Anyways, you should be able to have almost everything completed automatically for you. If you create a setup project (MSI) in Visual Studio and add the "Project Output" of your application to the location on the customer's machine that you want it, Visual Studio will automatically pick up necessary MSMs and add them and thier dependents to your setup project. If this does not happen, let me know and I can give you a list of all MSMs you will need to add manually to your project.
- Jeff
NI
PS - I would also like to know why your help system is not functioning. Can you explain a little more how this happened?
02-27-2006 03:53 AM
Thanks for your help Jeff.
I realise now that the pages I couldn't display were the ones that were trying to link to my MSDN help. It's no more than annoying - but I can find the relevent pages switching between help applications.
I am having problems finding the topic: "Optimizing Measurement Studio Graph .NET Controls". I would realy like to read this topic as I have a high throughput waveform that I need to imlpement as smoothely as possible.
It is referenced a few times in the board and in other comments, but it does not exist in my MS 7.0 help.
Regards ...