11-25-2007 12:32 AM
<assemblyIdentity name="NationalInstruments.Common" publicKeyToken="4544464CDEAAB541" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-8.1.20.237" newVersion="8.1.20.237" />
11-26-2007 10:29 AM
<configuration>
<runtime>
<assemblyBinding
xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity
name="NationalInstruments.Common">
publicKeyToken="4544464cdeaab541"
culture="neutral" />
<bindingRedirect
oldVersion="8.1.20.235">
newVersion="8.1.20.237" />
</dependentAssembly>
</assemblyBinding
</runtime>
</configuration>
11-26-2007 11:40 PM
11-27-2007 11:45 AM
Hi Joe,
To address your first, implicit question, yes, several of our assemblies do
have other file dependencies. We actually explicitly mention which ones in our Deploying
Measurement Studio Applications help topic in the NI Measurement Studio
Help. Inside that category, there is a section entitled Measurement
Studio .NET XCOPY Deployment Files that displays a table which shows you
file dependencies. Make sure to review this list when deploying to ensure
that all the correct files are deployed.
When we came out with ASP.NET support, we decided to only make a website
template and not a web application template. However, we did do some
basic testing with Web Applications to make sure that our components work
correctly and they did. The reason you don't see the App_Licenses.dll file in the web application project
is because web applications follow the same licensing schema as Windows Forms.
In this case, the licenses.licx file gets embedded directly into the assembly that is
created. If you are curious about differences, Microsoft has a document
entitled Introduction
to Web Application Projects which has a section on the differences between
web site projects and web application projects.
From a web site perspective, we have a topic that talks about licensing in our
help entitled Deploying Measurement Studio Web Applications.
Hope this clarifies things!
Best Regards,