APP_License.dll can not be generated automatically in ASP.NET website - by Jamebo

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 499908 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 10/23/2009 1:20:33 AM
Access Restriction Public

Description

Put a 3rd commercial web control into a new website. THe licenses.licx can be generated automatically. After run, the app_license.dll can not be generated and the control will throw license exception. 
(This bug is just in website. In a web application, the license checking will be run correctly.)
Sign in to post a comment.
Posted by Amy [MSFT] on 11/20/2009 at 11:04 AM
There is another bug tracking the generation of licenses.licx which should be fixed for the final release
Posted by Jamebo on 11/3/2009 at 5:02 PM
>>In Websites, App_LICENSES.dll is generated to contain the LICX as an embedded resource.
Yes, that is the feature what VS2008 provided.
But in VS2010 Beta2, I can not get this result. Please check it.

>>In Websites, App_LICENSES.dll is generated to contain the LICX as an embedded resource.
It sounds this is not current (VS2008) behavior.
Current bebavior (VS2008) is generating WebApplication.dll which contains embed license resource, not copy the lic file to /bin folder.
Please confirm that.

Thanks
-Jamebo
Posted by Amy [MSFT] on 11/3/2009 at 1:30 PM
In a web application project, manually copy the .lic file to /bin folder. In a Website, this is done automatically.

At this pointm refresh the designer or rerun the project and the licensed control should work as expected.

Note: App_LICENSES.dll isn't required in a WAP. In Websites, App_LICENSES.dll is generated to contain the LICX as an embedded resource. In WAP, there is a project assembly which contains the embedded LICX resource, so a separate DLL is not necessary
Posted by Microsoft on 10/27/2009 at 1:05 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you
Posted by Microsoft on 10/25/2009 at 8:36 PM
Thank you for your feedback, We are currently reviewing the issue you have submitted.