Hi - I have successfully wasted several hours now looking for a definitive document that will give the procedural steps for creating a PA zip file of a module that has been created in VB under  VS2008, but without including the SOURCE ascx.vb Files. Sadly I have not found where this is explained.

I've no doubt there must be one somewhere (surely?) and I am sure I am being blind as a bat, but , if anyone can point me in the direction of this information I would be very obliged.

[I cannot believe it is so hard to find this information on a simple Search. There are one or two other developers of modules I see who have asked this very same question but without getting a proper answer.]

 

Hi Chris - many thanks for replying. I don't actually want the source vb file to be included as I would like customers to receive the PA zip with the functionality but no ascx.vb files. Presumably I would need to get VS2008 to build a DLL and include this in the PA zip file under a BIN directory?  

If you are developing in WSP and need to ship as a PA several things will need to be done.

First you will need to create a class project for the module – this will provide the means to compile the dll - and copy all the code behind files to it, add references for all the web controls in each file effectively correcting any compile errors; then open all the ascx/aspx files and replace CodeFile with CodeBehind and package.

---

Robert Harriman
WEBMAZING.NET
AutoWebSuite / BrokerWebSuite
DNN Modules for Auto Dealers and Real Estate Professionals.