Re: What is Needed to Get an ASP.NET Page to Work?

Oh, I wasn't aware that there was an option in vs to do this.

Now I use web deployment projects which give me more control over
dev/production config section replacements, which was a large issues as
I developed one app on a pc,laptop and remote machine.

thanks!

Mark E. Hansen wrote:
On 10/11/06 06:19, Sean Chambers wrote:
There is other dll's that need to be included in addition to
MyProject.dll, basically everything in the bin folder after compiling,
minus the .pdb files, these are for debugging purposes.

Besides the entire bin folder, and any aspx pages, it should work fine.
The key is the entire bin folder though. Or at least this is what I
have found.

Also, everytime you compile an asp.net 2.0 website, a number of dll
files are generated that are pre-compiled aspx pages, EVERYTIME you
compile, these change. This is why you have to replace the entire bin
folder.

If you don't want it to pre-compile each aspx, you can get the "Web
Deployment Projects" from msdn that gives you additional deployment
options such as compiling all pages into a single DLL, I use that now
as it is much easier than managing all the seperate dll files.

Sean,

I don't know if this will help your situation, but there is a setting
in the project properties that governs how the generated component DLL
files are named. I've selected "Use fixed naming and single page assemblies"
and no longer get the random DLL file names. They are named based on the
page name.

FYI.


Altemir wrote:
SOME BACKGROUND:

I am new to ASP.NET, but somehow managed to install a perfectly working
.aspx page on our production server that I compiled in Visual Studio.
However, I recently needed to update it, so I first added a ".old"
suffix to the MyPage.aspx, MyProject.dll, and global.asax files on the
production server so I had a backup copy of the original files in case
something went wrong. Indeed, something did go wrong when I installed
the files on the production server, so I deleted the ".old" suffixes to
return the application to its original state ... AND NOW IT DOESN"T
WORK?!!?!?!

I get Parser Error messages like "Could not load type
'MyProject.MyPage' " and "Could not load type 'MyProject.Global' " I
do not have this problem on my localhost, EXCEPT when I try to copy the
application into a different test directory on my localhost. Which
leads me to ...

MY QUESTION:

What exactly is needed on a host to make an .aspx page work? I was
under the impression that all you need are fully compiled (built)
.aspx, .dll, and .asax files. I thought you could just copy these
anywhere and they would work together (provided that they're in the
right folders).

What am I misunderstanding?


.

Relevant Pages

  • Re: Namespaces - broad question
    ... aspx pages that I know I want utilize a specific function within, ... have the same codebehind page), how can I reference this function. ... >> compiling if the same class was written in different places. ... > A .Net assembly is a compiled DLL. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Namespaces - broad question
    ... > compiling if the same class was written in different places. ... A .Net assembly is a compiled DLL. ... your CodeBehind class files are ... > contained in a codebehind page that was NOT referenced by the aspx page? ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: What is Needed to Get an ASP.NET Page to Work?
    ... MyProject.dll, basically everything in the bin folder after compiling, ... Besides the entire bin folder, and any aspx pages, it should work fine. ... Also, everytime you compile an asp.net 2.0 website, a number of dll ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: DLL Question
    ... I would say the same thing that it should be in the bin folder, ... whatever file you are compiling) and look at the Build Action property. ... In the Visual Studio .NET Solution Explorer, ... How would I take my class and turn it into a DLL to ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Encrypting the source code
    ... What Jim is saying is: You only need to deploy the following files: *.aspx, ... *.asax, Web.config, and *.dll (from the bin folder); ...
    (microsoft.public.dotnet.framework.aspnet.security)
Loading