Deploying ASP.NET application

[jwk]

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.

[Scott Allen]

Hi jwk:

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

--
Scott
http://www.OdeToCode.com/blogs/scott/
On Fri, 25 Mar 2005 07:27:02 -0800, jwk
<jw*@discussion s.microsoft.com > wrote:

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.

[jwk]

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

"Scott Allen" wrote:

Hi jwk:

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

--
Scott
http://www.OdeToCode.com/blogs/scott/
On Fri, 25 Mar 2005 07:27:02 -0800, jwk
<jw*@discussion s.microsoft.com > wrote:

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.

[Tampa.NET Koder]

You probably have seen this already; but it may help others.
http://msdn.microsoft.com/library/de...plications.asp

Have you tried copying the Crystal Assemblies to the Bin directory? I think
Crystal Reports assemblies are deployed in the GAC so it doesn't copy the
necessary assemblies to your bin directory.

Hope any of this information helps


"jwk" <jw*@discussion s.microsoft.com > wrote in message
news:80******** *************** ***********@mic rosoft.com...

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

"Scott Allen" wrote:

Hi jwk:

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

--
Scott
http://www.OdeToCode.com/blogs/scott/
On Fri, 25 Mar 2005 07:27:02 -0800, jwk
<jw*@discussion s.microsoft.com > wrote:

>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.

[Scott Allen]

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.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Fri, 25 Mar 2005 07:49:09 -0800, jwk
<jw*@discussion s.microsoft.com > wrote:

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

"Scott Allen" wrote: