Issues with Visual Studio .NET 2005 and Measurement Studio?

[Shea24]

We are beginning development on an application with Measurement Studio and .NET 2003. Since we're still in the early stages of development, switching over to a .NET 2005 beta, with eventual migration to the final release, is an option.

Does anybody know of any issues with Measurement Studio and VS .NET 2005? C# is our language of choice (not that it really matters anymore...)

Thanks.

[Elton Wells]

Measurement Studio 7.0 and 7.1 were not tested with the Visual Studio .NET 2005 beta, so using Measurement Studio 7.0 or 7.1 in the Visual Studio .NET 2005 beta is at your own risk.

Having said that, though, we have tried to use Measurement Studio 7.1 (after it was released) in the Visual Studio .NET 2005 beta just to see what happens. The biggest problem that we know of that you might run into is that licensing for analysis does not work. The auto format design-time feature for the UI controls also does not work. Also, the Measurement Studio integration features (menu, project wizards, etc.) will not work.

If you decide to proceed with using Measurement Studio 7.1 in the Visual Studio .NET 2005 beta and you find additional problems, please either post them to this forum or report them to support. This way we can be sure to verify that the problem is resolved for the release version of Visual Studio .NET 2005 in a future release of Measurement Studio. Thanks.

- Elton

[drohacek]

As Elton mentioned, we will be supporting Visual Studio .NET 2005 in an upcoming version of Measurement Studio. Easy migration from Measurement Studio 7.1 and Visual Studio .NET 2003 to the next version of Measurement Studio and Visual Studio .NET 2005 is a goal of that release (with respect to Measurement Studio libraries).

You can sign up for the beta of the next version of Measurement Studio at ni.com/beta. The beta will not be licensed for deployment, so as you consider your options, please take into account the fact that Measurement Studio components that support Visual Studio .NET 2005 will most likely not be available for a production application until some time after Visual Studio .NET 2005 releases.

[ALindenthal]

Hello,

Microsoft gives now a "Go Live" license for Visual Studio 2005 Beta 2. Can we expect although a solution from Measurement Studio to deploy before the offical release (end of this year) comes out.

All my other components still support Visual Studio 2005 Beta.

Best regards

Andreas Lindenthal

[Nate D'Anna]

Greetings,

We currently do not have plans to offer a similar license to the "Go Live" now offered by Microsoft. If you can please elaborate on your use case, it will help us consider such a license.

Best,
Nate D'Anna

[dfsht]

Measurement Studio does not work under VS 2005 beta 2, because of component licensing. (run time license error)

System.Security.Cryptography.CryptographicException was unhandled
Message="Length of the data to decrypt is invalid."
Source="mscorlib"
StackTrace:
at System.Security.Cryptography.RijndaelManagedTransform.TransformFinalBlock(Byte[] inputBuffer, Int32 inputOffset, Int32 inputCount)

at System.Security.Cryptography.CryptoStream.FlushFinalBlock()

at System.Security.Cryptography.CryptoStream.Dispose(Boolean disposing)

at System.IO.Stream.Close()

at System.IO.Stream.System.IDisposable.Dispose()

at NationalInstruments.Restricted.LicenserHelper.Decrypt(String cypherText)

at NationalInstruments.Restricted.LicenseBase.a(String )

at NationalInstruments.Restricted.LicenseBase.RunTimeCheck(LicenseContext context, Type type)

at NationalInstruments.Restricted.LicenseProviderBase.GetLicense(LicenseContext context, Type type, Object instance, Boolean allowExceptions)

at System.ComponentModel.LicenseManager.ValidateInternalRecursive(LicenseContext context, Type type, Object instance, Boolean allowExceptions, License& license, String& licenseKey)

at System.ComponentModel.LicenseManager.ValidateInternal(Type type, Object instance, Boolean allowExceptions, License& license)

at System.ComponentModel.LicenseManager.Validate(Type type, Object instance)

at NationalInstruments.UI.WindowsForms.Led..ctor()

at WindowsApplication2.Form1.InitializeComponent() in I:\temp\WindowsApplication2\WindowsApplication2\Form1.Designer.cs:line 40

at WindowsApplication2.Form1..ctor() in I:\temp\WindowsApplication2\WindowsApplication2\Form1.cs:line 15

at WindowsApplication2.Program.Main() in I:\temp\WindowsApplication2\WindowsApplication2\Program.cs:line 16

at System.AppDomain.nExecuteAssembly(Assembly assembly, String[] args)

at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)

at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()

at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Threading.ThreadHelper.ThreadStart()

[ALindenthal]

Hello,

we plan to release a new software at the end of August. Now we decide to switch to Visual Studio 2005 Beta 2 and make the release with this version, because it should be stable and we must not change two month later after the first release.

All of our components have versions for Visual Studio 2005 Beta 2. Like I heard are you not planning to support Visual Studio 2005 Beta 2 with Measurement Studio 7.1. So we think to use your next Beta - Version of Measurement Studio which hopefully support Visual Studio 2005 Beta 2. But this version to told we can't deloy until it is released. This is a problem for us.

We have a subcription of Measurement Studio and we need a solution. Best way is to support Visual Studio 2005 Beta 2 with Measurement Studio 7.1.

Best regards

Andreas

[bilalD]

Hi See this post for more information about the new Measurement Studio 8.0.1 and VS 2005 support.

[Stephane]

Try this patch http://digital.ni.com/softlib.nsf/websearch/58142402AAA023B4862570C7007AE4FB?opendocument&node=13206...

It should fix your problem. And only use  c++ components OR national intrument components, don't use both.