05-10-2010 10:03 AM
Solved! Go to Solution.
05-12-2010 09:42 AM
DN 2.0 is the .NET 2.0 framework. Diadem requires at least the 2.0 version, so it is included in the installer.
-Christina
05-12-2010 10:23 AM
05-13-2010 05:57 PM
Joe,
I agree; that is quite strange. I have referred your question to the Diadem R&D team, but there is some delay for them to respond, as they are in Germany. However, I do have a few more questions for you: what operating system are you using, and do you have any other versions of the .NET framework installed? Also, were any of them installed prior to installing Diadem?
Thanks for the information,
-Christina
05-14-2010 03:59 AM
This was with Windows 'XP. It was installed on a "clean machine" that I built earlier that morning. I believe that it had .NET 1.1 (SP1) and .NET 3.5 on it as well.
The portion of the application that needs .NET 2.0 is somewhere within my application and not tied to DIAdem, however we found through experimentation that installing DIAdem indirectly solves the problem.
05-17-2010 11:16 AM
Joe,
The .NET 2.0 part of the installer simply checks for current versions of the framework on your computer and then the DN 2.0 actually installs it. Sorry for the confusion about the two parts that seemingly install the same component. Our installers team is aware of the potential for confusion with this namine and will be modifying it so that this type of confusion hopefully doesn't come up in the future.
If you uninstall DIAden and install just the .NET framework 2.0 does you application work?
-Christina
05-25-2010 08:11 AM
I actually built another clean machine and installed my LabVIEW application and .NET 2.0 (but not DIAdem), and everything worked okay, so I'm guessing the answer to your question is Yes, but I have not performed that specific experiment.
Joe