The file '/Default.aspx' has not been pre-compiled, and cannot be requested.
Trying to do a patch release.
Site built with Web deployment projects. It is set to be not updatable (which I believe means it will compile everything into a DLLs right?).
I am trying to update a 3rd party dll. I go into every bin folder that has it and copy the newest version into each folder.
I checked my web.config file to ensure that my 3rd party dll does not have version specified in it, which it doesn't. We are not using multilpe version of the dlll. One version only.
When I try to run the site I get
The file '/Default.aspx' has not been pre-compiled, and cannot be requested.
What does this mean and how can I resolve it?
Thanks,
Angela
Site built with Web deployment projects. It is set to be not updatable (which I believe means it will compile everything into a DLLs right?).
I am trying to update a 3rd party dll. I go into every bin folder that has it and copy the newest version into each folder.
I checked my web.config file to ensure that my 3rd party dll does not have version specified in it, which it doesn't. We are not using multilpe version of the dlll. One version only.
When I try to run the site I get
The file '/Default.aspx' has not been pre-compiled, and cannot be requested.
What does this mean and how can I resolve it?
Thanks,
Angela
ASKER
Thanks so much for your response :)
Is there anyway to release patched versions of it?
Ie windows constantly updates there DLLS... Many pieces of software use those DLLs. When windows updates your machine, you are not required to recompile every piece of software that is installed inorder to get it to work.
This is the scenario I want to do?
Is there anyway to release patched versions of it?
Ie windows constantly updates there DLLS... Many pieces of software use those DLLs. When windows updates your machine, you are not required to recompile every piece of software that is installed inorder to get it to work.
This is the scenario I want to do?
I know what you mean, but if the application is precompiled, it used a specific version of the 3rd party library while compiling. It's like the 3rd party dll becames part of your dll.
A way to "patch" it, would be to have separate projects, thus separate .dlls, instead of one big application. Then, you can deploy smaller projects.
Another way, NOT recommended, would be to just copy your site, uncompiled. ASP.NET compiles files on the fly if needed, so that why you can do it this way.
A way to "patch" it, would be to have separate projects, thus separate .dlls, instead of one big application. Then, you can deploy smaller projects.
Another way, NOT recommended, would be to just copy your site, uncompiled. ASP.NET compiles files on the fly if needed, so that why you can do it this way.
ASKER
Hi Juan,
Right now we have 6 different projects in one solution. Each having this DLL in its bin directories.
When I look at the output for the release folder for the entire site. I see it still has the third party dll in its bin directory. So, it doesn't appear to be merign the thrid party dll in with the overal projects.
Again I really appreciate your help,
Angela
Right now we have 6 different projects in one solution. Each having this DLL in its bin directories.
When I look at the output for the release folder for the entire site. I see it still has the third party dll in its bin directory. So, it doesn't appear to be merign the thrid party dll in with the overal projects.
Again I really appreciate your help,
Angela
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you
remove your asp.net templorary files and runit in prod.
You get that error because the site was compiled against the older version of your 3rd party dll.