Deploying ASP.NET application

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have built my project using a "deployment project" - I've added all the
correct Merge Modules as well as Primary Output and Content Files from
'Project Outputs' ; but the aspx pages still refer to dll's which are not
separately included in the build (ie they are CrystalReports dll's which I
can see from the build output have all been 'packaged' into the build).

When I build the project in the Deployment Project it does not alter the
page directive at the top of the aspx pages which still refer to dll's which
have been 'packaged'. Thus I'm getting errors when I try load the aspx page.
 
Hi jwk:

Why does the @ Page directive need to change? It should be the same in
development as it is after deployment.
 
Hi Scott,

The problem is that when I build the deployment project I just add the
Crystal Reports Merge Modules as required (these appear to add the dll's
into the main assembly). Thus the original dll's are not included in the bin
directory of the built project.

The assemblies referred to in the page directive have thus not been included
in the build bin directory
 
If I remember, adding the right merge module (I think there were 2)
worked for me, although there was the trick of entering a license key
into the properties for one of the modules.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top