MStudio.NET breaks the VS.NET development environment?

[ValyaS]

How to assure that after installing MStudio.NET on my machine, all projects previously built with VS.NET will still compile without changes?

I've hade a terrible experience a year ago when the Trial version of the MStudio overwrote all my VS.NET development environment and I lost control over my old VS.NET project (which I have to still SUPPORT!)
I've read about fixing the "feature" of overwriting the Directory Paths in the version 7.1 but still want a very minimum affects of MStudio.NET to my VS.NET.

[drohacek]

The intention of the Measurement Studio feature that you are referring to is to add the Measurement Studio Include and Lib paths to the Visual C++ list of Include and Lib paths. There was a bug in Measurement Studio 7.0 that caused the Measurement Studio integration startup code to overwrite the predefined Visual C++ compiler Include and Library paths under a particular Visual Studio install and usage scenario prior to Measurement Studio installation. The workaround for this particular bug was to add the Visual C++ Include and Library paths back manually, via the Tools>>Options dialog box. This particular bug has been fixed in Measurement Studio 7.1 such that existing Include and Lib paths should no longer be overwritten under any install and usage scenario. Additionally, the particular Visual Studio install scenario that caused the bug to manifest has been added to our test suite.

Note that this bug affected only Visual C++ projects and not C# or VB.NET projects. Is this the bug that you are referring to or was there something else that actually changed your project settings?

If you are still concerned about Measurement Studio integration startup code, you can choose to not install Measurement Studio integration features. To do this, uncheck Measurement Studio Visual C++ .NET Support>>Visual C++ .NET 2003 Integration Tools in the installer feature tree. Note that this means that you will not have access to any Measurement Studio integration features including wizards, menu items, and assistants. You will need to add the Measurement Studio Include and Lib paths to the Visual C++ environment settings or your project settings manually.

[ValyaS]

Thanks for your reply.

If I'll un-check the "Measurement Studio Visual C++ .NET Support>>Visual C++ .NET 2003 Integration Tools" option during the installation, will I still be able to use MStudio controls and tools in other projects (C# and VB.NET)?

Here is my situation:
- I have an internal project that should use MStudio for building a .NET application (with C# only.)
- Also I have a lot of different developed earlier VS.NET projects (in C#, VB.NET, C) that I should support and deploy updates to customers as an SDK (with source code, solutions and projects files.)

What would be the best way for installation MStudio?

Is it there an option after installing MStudio to disable it temporary to not to affect pure VS.NET projects and solutions?



Valentina

[drohacek]

If I'll un-check the "Measurement Studio Visual C++ .NET Support>>Visual C++ .NET 2003 Integration Tools" option during the installation, will I still be able to use MStudio controls and tools in other projects (C# and VB.NET)?
Yes, if you un-check the Visual C++ .NET 2003 Integration Tools, the .NET libraries and integration tools are still installed and usable. If you do not want to install the .NET integration tools, you'll need to un-check Measurement Studio .NET Languages Support>>Visual Studio .NET 2003 Integration. If you install in this manner, without any integration support, you can use Measurement Studio .NET libraries just like you use any other libraries. You will have to manually add references to the Measurement Studio libraries from your .NET projects. If you want the controls in the toolbox, you'll need to add them there manually. One last gotcha if you do not install the integration tools has to do with licensing. The user interface controls will license properly, but if you use the analysis libraries, you will have to manually add license information to the project's .licx file. The Measurement Studio help contains detailed information about how to do this; from the table of contents, go to NI Measurement Studio Help>>NI Measurement Studio .NET Class Library>>Using the Measurement Studio .NET Class Libraries>>Licensing Measurement Studio .NET Class Libraries.

Here is my situation:
- I have an internal project that should use MStudio for building a .NET application (with C# only.)
- Also I have a lot of different developed earlier VS.NET projects (in C#, VB.NET, C) that I should support and deploy updates to customers as an SDK (with source code, solutions and projects files.)

What would be the best way for installation MStudio?

In this scenario, you are not using the Measurement Studio C++ class libraries at all. If that is the case, I recommend that you install only .NET support. In the installer feature tree, un-check Measurement Studio Visual C++ .NET Support.

Is it there an option after installing MStudio to disable it temporary to not to affect pure VS.NET projects and solutions?

By this, I assume that you want to know if there is a way to disable Measurement Studio integration features. To do this in Visual Studio .NET 2003, go to Tools>>Add-in Manager and un-check Measurement Studio AddIn.

[ValyaS]

I just installed MStudio like you suggested and it didn't break any thing in the VS.NET 😉


Thank you, drohacek!

Valentina

[drohacek]

You're welcome. Let us know if you encounter any issues or have any questions.