The bass class System.Web.UI.Page cannot be designed.

Help!!

I am now getting the following error concerning the Microsoft Development Environment in .NET:

=========================================================
The file failed to load in the Web Form designer. Please correct the following error, then load it again: The designer could not be shown for this file because none of the classes within it can be designed. The designer inspected the following classes in the file:

contactbroker -- The base class 'System.Web.UI.Page' cannot be designed.
=========================================================

What do I need to do. This happens with all of my .aspx pages not just the one listed in the error message. Is there another reference I need to load into my solution. I currently have the following reference listed:

Microsoft.Web.UI.WebControls
MSHTML
stdole
System
System.Data
System.Drawing
System.Security
System.Web
System.Web.ReqularExpressions
System.Web.Services
System.Windows.Forms
System.XML
tabDlg

I hope this is enought info to help you figure out what my problem is, other than be too ignorant to figure it out for myself...

Thanks

ArtAre you trying to build a page class in a usercontrol?
I guess I don't even know enough to understand your question. Can you help me out a little further? Thanks
Yeah, that was a bad response on my part. Basically, are you trying to do things in an ascx file that should are meant for aspx. If you are working in an aspx page, you can use the system.web.ui.page, but if you are in a usercontrol (ascx) you must make use of system.web.ui.usercontrol or whatever. Also remember (Just a heads up, not releated to your current problem), a page can only have one form tag and your ascx files cannot have a form tag because this is used in the page which those usercontrols will sit inside of.
Here is my situation. I installed .NET Framework 1.1 yesterday. I already had .NET Framework 1.0 installed. I installed 1.1 because I wanted to take advantage of the HasRows Property when check to see if a dataReader had returned any rows. After I installed 1.1 I got an error on the HasRows property. I then removed the version 1.0 System.Data, System.Drawing, System.Security, System.Web, System.Web.RegularExpressions, System.WebServices, and System.XML references and replaced them all with 1.1 version. Well the HasRows problem went away but now, every time I try to open one of my .aspx pages I get the error that is the subject of this post. Additoinally I can no longer get into the design mode for any of these forms.

I haven't changed any of the code, or added any additional references to the project.
What version of Visual Studio are you using?
Microsoft Development Environment 2002 Version 7.0.94466

The correct syntax for returning a DataSet

I realise this is a beginners question but i would be grateful for some help
Untill now i have been using Datareaders for example;
Public Class Catalog
Public Shared Function SP_GetBB() As SqlDataReader
' Create the connection object
Dim connection As New SqlConnection(ConnectionString)
' Create and initialize the command object
Dim command As New SqlCommand("SP_GetBB", connection)
command.CommandType = CommandType.StoredProcedure
' Open the connection
connection.Open()
' Return a SqlDataReader to the calling function
Return command.ExecuteReader(CommandBehavior.CloseConnection)
End Function
Can anyone tell me how to convert the above to return a Dataset
I have got this far but am not sure how to finish:
Public Class Catalog
Public Shared Function SP_GetBB() As System.Data.DataSet
' Create the connection object
Dim connection As New SqlConnection(ConnectionString)
' Create and initialize the command object
Dim command As New SqlCommand("SP_GetBB", connection)
command.CommandType = CommandType.StoredProcedure.......
...........................
many thanks
martin
Message posted via webservertalk.com
http://www.webservertalk.com/Uwe/Fo...sp-net/200510/1Hi Martin,
you need a DataAdapter to fill your DataSet, for example:
Public Function SelectSqlSrvRows(dataSet As DataSet, connection As String,
query As String) As DataSet
Dim conn As New SqlConnection(connection)
Dim adapter As New SqlDataAdapter()
adapter.SelectCommand = new SqlCommand(query, conn)
adapter.Fill(dataset)
Return dataset
End Function
For a description look at
http://msdn.microsoft.com/library/d...op
ic.asp
Alex
http://www.DotNet42.com - The Answer to Your DotNet question
"martinharvey via webservertalk.com" wrote:

> I realise this is a beginners question but i would be grateful for some he
lp
>
> Untill now i have been using Datareaders for example;
> Public Class Catalog
> Public Shared Function SP_GetBB() As SqlDataReader
> ' Create the connection object
> Dim connection As New SqlConnection(ConnectionString)
> ' Create and initialize the command object
> Dim command As New SqlCommand("SP_GetBB", connection)
> command.CommandType = CommandType.StoredProcedure
> ' Open the connection
> connection.Open()
> ' Return a SqlDataReader to the calling function
> Return command.ExecuteReader(CommandBehavior.CloseConnection)
> End Function
> Can anyone tell me how to convert the above to return a Dataset
> I have got this far but am not sure how to finish:
>
> Public Class Catalog
> Public Shared Function SP_GetBB() As System.Data.DataSet
> ' Create the connection object
> Dim connection As New SqlConnection(ConnectionString)
> ' Create and initialize the command object
> Dim command As New SqlCommand("SP_GetBB", connection)
> command.CommandType = CommandType.StoredProcedure.......
> ...........................
> many thanks
> martin
>
> --
> Message posted via webservertalk.com
> http://www.webservertalk.com/Uwe/Fo...sp-net/200510/1
>
Alex wrote:
>Hi Martin,
>you need a DataAdapter to fill your DataSet, for example:
>Public Function SelectSqlSrvRows(dataSet As DataSet, connection As String,
>query As String) As DataSet
> Dim conn As New SqlConnection(connection)
> Dim adapter As New SqlDataAdapter()
> adapter.SelectCommand = new SqlCommand(query, conn)
> adapter.Fill(dataset)
> Return dataset
>End Function
>For a description look at
>http://msdn.microsoft.com/library/d...o
pic.asp
>Alex
>http://www.DotNet42.com - The Answer to Your DotNet question
>
>[quoted text clipped - 29 lines]
many thanks for your help with this
Cheers
martin
Message posted via http://www.webservertalk.com

The correct syntax for returning a DataSet

I realise this is a beginners question but i would be grateful for some help

Untill now i have been using Datareaders for example;

Public Class Catalog
Public Shared Function SP_GetBB() As SqlDataReader

' Create the connection object
Dim connection As New SqlConnection(ConnectionString)
' Create and initialize the command object
Dim command As New SqlCommand("SP_GetBB", connection)
command.CommandType = CommandType.StoredProcedure
' Open the connection
connection.Open()
' Return a SqlDataReader to the calling function
Return command.ExecuteReader(CommandBehavior.CloseConnect ion)
End Function

Can anyone tell me how to convert the above to return a Dataset
I have got this far but am not sure how to finish:

Public Class Catalog
Public Shared Function SP_GetBB() As System.Data.DataSet
' Create the connection object
Dim connection As New SqlConnection(ConnectionString)
' Create and initialize the command object
Dim command As New SqlCommand("SP_GetBB", connection)
command.CommandType = CommandType.StoredProcedure.......
...........................

many thanks

martin

--
Message posted via DotNetMonster.com
http://www.dotnetmonster.com/Uwe/Fo...sp-net/200510/1Hi Martin,

you need a DataAdapter to fill your DataSet, for example:

Public Function SelectSqlSrvRows(dataSet As DataSet, connection As String,
query As String) As DataSet
Dim conn As New SqlConnection(connection)
Dim adapter As New SqlDataAdapter()
adapter.SelectCommand = new SqlCommand(query, conn)
adapter.Fill(dataset)
Return dataset
End Function

For a description look at
http://msdn.microsoft.com/library/d...lasstopic.a sp

Alex

http://www.DotNet42.com - The Answer to Your DotNet question

"martinharvey via DotNetMonster.com" wrote:

> I realise this is a beginners question but i would be grateful for some help
>
> Untill now i have been using Datareaders for example;
> Public Class Catalog
> Public Shared Function SP_GetBB() As SqlDataReader
> ' Create the connection object
> Dim connection As New SqlConnection(ConnectionString)
> ' Create and initialize the command object
> Dim command As New SqlCommand("SP_GetBB", connection)
> command.CommandType = CommandType.StoredProcedure
> ' Open the connection
> connection.Open()
> ' Return a SqlDataReader to the calling function
> Return command.ExecuteReader(CommandBehavior.CloseConnect ion)
> End Function
> Can anyone tell me how to convert the above to return a Dataset
> I have got this far but am not sure how to finish:
>
> Public Class Catalog
> Public Shared Function SP_GetBB() As System.Data.DataSet
> ' Create the connection object
> Dim connection As New SqlConnection(ConnectionString)
> ' Create and initialize the command object
> Dim command As New SqlCommand("SP_GetBB", connection)
> command.CommandType = CommandType.StoredProcedure.......
> ...........................
> many thanks
> martin
>
> --
> Message posted via DotNetMonster.com
> http://www.dotnetmonster.com/Uwe/Fo...sp-net/200510/1
Alex wrote:
>Hi Martin,
>you need a DataAdapter to fill your DataSet, for example:
>Public Function SelectSqlSrvRows(dataSet As DataSet, connection As String,
>query As String) As DataSet
> Dim conn As New SqlConnection(connection)
> Dim adapter As New SqlDataAdapter()
> adapter.SelectCommand = new SqlCommand(query, conn)
> adapter.Fill(dataset)
> Return dataset
>End Function
>For a description look at
>http://msdn.microsoft.com/library/d...lasstopic.a sp
>Alex
>http://www.DotNet42.com - The Answer to Your DotNet question
>> I realise this is a beginners question but i would be grateful for some help
>>
>[quoted text clipped - 29 lines]
>>
>> martin

many thanks for your help with this

Cheers

martin

--
Message posted via http://www.dotnetmonster.com

The directory /App_Code is not allowed because the application is precompiled

I'm using VS.NET 2005 Beta 2. I have a helper C# class I wrote that I placed
in my /App_Code directory. Everything runs fine locally. However when I
use the "Copy Web" function to upload the site to the production server, I
get the following error when trying to run the page on production:
"System.Web.HttpException: The directory '/App_Code' is not allowed
because the application is precompiled."
Anyone know this works fine locally but not on development? How can I
resolve this?
Also on a related note I read a lot about a new "\code" directory in ASP.NET
2.0. Am I correct to assume that at some point they changed this from \code
to \App_Code and these are the same thing?
SteveHi, Steve.
re:
> Am I correct to assume that at some point they changed this from \code to
\App_Code and
> these are the same thing?
You're correct. In Beta 1 it was called /code.
In Beta 2, it was changed to /App_Code.
See http://msdn.microsoft.com/asp.net/w...eta2update.aspx
for a complete list of special directories.
re:
> "System.Web.HttpException: The directory '/App_Code' is not allowed becau
se the
> application is precompiled."
> Anyone know this works fine locally but not on development? How can I resolve thi
s?
You don't need to resolve it.
Because you're precompiling, everything that would go in the App_Code
directory is already compiled and doesn't need to be uploaded.
If you want to upload your source files into the
App_Code directory, don't precompile your application.
Juan T. Llibre
ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
==========================
"Steve Franks" <please@.postreplyhere.com> wrote in message
news:dfKdnTtsD5yXYLneRVn-jQ@.comcast.com...
> I'm using VS.NET 2005 Beta 2. I have a helper C# class I wrote that I plac
ed in my
> /App_Code directory. Everything runs fine locally. However when I use th
e "Copy Web"
> function to upload the site to the production server, I get the following
error when
> trying to run the page on production:
> "System.Web.HttpException: The directory '/App_Code' is not allowed becau
se the
> application is precompiled."
> Anyone know this works fine locally but not on development? How can I res
olve this?
> Also on a related note I read a lot about a new "\code" directory in ASP.N
ET 2.0. Am I
> correct to assume that at some point they changed this from \code to \App_
Code and these
> are the same thing?
> Steve
>
>
> Because you're precompiling, everything that would go in the App_Code
> directory is already compiled and doesn't need to be uploaded.
> If you want to upload your source files into the
> App_Code directory, don't precompile your application.
>
I am not purposely precompiling my application. How can I prevent it from
precompiling?
Locally I just use VS.NET 2005 b2 to do the development and press F5 to run
it. Sometimes I press F6 to get a sanity check on whether I've screwed any
code up.
For production, I want the flexibility to be able to edit source on the
production server to make an update on the fly, so the precompiled approach
is not of interest.
My main goal is to just be able to easily synchronize the work I do at home
on the production server, and then get to work and easily update my local
dev copy of the web app to reflect the changes I've made at home by syncing
with the production server. Then I'll make changes at work, and when I get
home, I'll want to sync my home machine up with what's now on the production
server, and so forth. Currently I'm (trying) to use the Copy Web function
for this. Is that appropriate and/or is there a better way?
Thanks,
Steve
Juan,
Any ideas about what I posted below? Looking forward to your response. Than
you so much.
Steve,
"Steve Franks" <please@.postreplyhere.com> wrote in message
news:H_qdnYfD0ILDNrjeRVn-hQ@.comcast.com...
> I am not purposely precompiling my application. How can I prevent it from
> precompiling?
> Locally I just use VS.NET 2005 b2 to do the development and press F5 to
> run it. Sometimes I press F6 to get a sanity check on whether I've
> screwed any code up.
> For production, I want the flexibility to be able to edit source on the
> production server to make an update on the fly, so the precompiled
> approach is not of interest.
> My main goal is to just be able to easily synchronize the work I do at
> home on the production server, and then get to work and easily update my
> local dev copy of the web app to reflect the changes I've made at home by
> syncing with the production server. Then I'll make changes at work, and
> when I get home, I'll want to sync my home machine up with what's now on
> the production server, and so forth. Currently I'm (trying) to use the
> Copy Web function for this. Is that appropriate and/or is there a better
> way?
> Thanks,
> Steve
>
I would check your web project's properties under MSBuild.
-Brock
DevelopMentor
http://staff.develop.com/ballen

> I am not purposely precompiling my application. How can I prevent it
> from precompiling?
> Locally I just use VS.NET 2005 b2 to do the development and press F5
> to run it. Sometimes I press F6 to get a sanity check on whether I've
> screwed any code up.
> For production, I want the flexibility to be able to edit source on
> the production server to make an update on the fly, so the precompiled
> approach is not of interest.
> My main goal is to just be able to easily synchronize the work I do at
> home on the production server, and then get to work and easily update
> my local dev copy of the web app to reflect the changes I've made at
> home by syncing with the production server. Then I'll make changes at
> work, and when I get home, I'll want to sync my home machine up with
> what's now on the production server, and so forth. Currently I'm
> (trying) to use the Copy Web function for this. Is that appropriate
> and/or is there a better way?
> Thanks,
> Steve
>
Well, there seems to be some sort of a conflict or design issue here with
this restriction.
I decided I'd just delete my App_Code directory from the remote site. I
figured this would be OK since its tellin gme the application is
precompiled. Yet then when I go to run a page it complains "The name
'myclass' does not exist in the current context". So if everything was
precompiled and no app_code directory is needed then what's the problem
here?
My preference is to precompile locally as I test and run my app, and then
when I publish to the remote server I want to publish all the files. I
can't seem to work around this. Any ideas?
Steve
"Brock Allen" <ballen@.NOSPAMdevelop.com> wrote in message
news:b8743b112290a8c7868466d649ee@.msnews
.microsoft.com...
>I would check your web project's properties under MSBuild.
> -Brock
> DevelopMentor
> http://staff.develop.com/ballen
>
>
re:
> My preference is to precompile locally as I test and run my app
I thought you had said you did *not* precompile.
There's a difference between "precompile" and "compile".
Which one are you doing ?
Have you tried to FTP your files instead of "publishing" them ?
Juan T. Llibre
ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
==========================
"Steve Franks" <please@.postreplyhere.com> wrote in message
news:gqqdnfBdIfGOFbrenZ2dnUVZ_s2dnZ2d@.co
mcast.com...
> Well, there seems to be some sort of a conflict or design issue here with
this
> restriction.
> I decided I'd just delete my App_Code directory from the remote site. I f
igured this
> would be OK since its tellin gme the application is precompiled. Yet then
when I go to
> run a page it complains "The name 'myclass' does not exist in the current
context". So
> if everything was precompiled and no app_code directory is needed then wha
t's the
> problem here?
> My preference is to precompile locally as I test and run my app, and then
when I publish
> to the remote server I want to publish all the files. I can't seem to wor
k around this.
> Any ideas?
> Steve
> "Brock Allen" <ballen@.NOSPAMdevelop.com> wrote in message
> news:b8743b112290a8c7868466d649ee@.msnews
.microsoft.com...
Sorry about the confusion. Let me explain specifically what I'm trying to
do.
Locally I'm using whatever the default settings are, as it relates to
precompiling. When I look at the property pages of my ASP.NET web
application, and click on the Build section, the revelant sections say
"Before running startup page: Build Web Site". And "Build solution action"
section has the check box checked for "Build web site as part of solution".
That is how I like to run things because I prefer to know about any mishaps
I've made coding-wise before the page runs.
Now over to production... I like the Copy Web function because it seems like
a convenient way from within VS.NET 2005 Beta 2 to easily have it sync the
production site with changes as I make them in development.
However recently I added a App_Code folder with a few utility classes I've
created. Now when I do the Copy Web the production site complains that the
App_Code folder is not allowed.
So my questions specifically are:
1) Is there a way where I can still use Copy Web in this scenario?
2) If not, how do I tell my local machine to not precompile and clear itself
from any precompiled files, so that when I do a copy web the remote site is
not in a precompiled mote? In other words, I assume my local machine has
the precompiled files that are being copied with Copy Web. So I do these
get deleted, and how do I set things set up locally so its no longer
prcompiled, so that my production server will be happy once I do a complete
Copy Web to try and straighten things out?
3) If I have to resort to a FTP copy, files with what extension should get
copied specifically? Or perhaps its easier toi look at it the other way -
which file extensions need to be deleted from the production server so it
does not see the web pages there as being "precompiled"?
Thanks so much. I'm looking forward to your answer as I have been stuck on
this for a few days. I really appreciate the help.
Steve
"Juan T. Llibre" <nomailreplies@.nowhere.com> wrote in message
news:OvKJFZOuFHA.2072@.TK2MSFTNGP14.phx.gbl...
> re:
> I thought you had said you did *not* precompile.
> There's a difference between "precompile" and "compile".
> Which one are you doing ?
> Have you tried to FTP your files instead of "publishing" them ?
>
> Juan T. Llibre
> ASP.NET MVP
> ASP.NET FAQ : http://asp.net.do/faq/
> ==========================
> "Steve Franks" <please@.postreplyhere.com> wrote in message
> news:gqqdnfBdIfGOFbrenZ2dnUVZ_s2dnZ2d@.co
mcast.com...
>
>
Hi, Steve.
What this sounds like is that, at some point, the "Publish Web Site"
tool was used instead of the "Copy Web" tool, and that the
"Allow this precompiled site to be updatable" option was not selected.
See : http://msdn2.microsoft.com/en-us/library/1y1404zt
for a step-by-step guide to using the "Publish Web Site" tool.
You can change the "Allow this site...to be updatable" option.
You might also want to take a look at the "Copying a website" walkthrough:
http://msdn2.microsoft.com/en-us/library/xay0wxbf
and at : http://msdn2.microsoft.com/en-us/library/1cc82atw
"Copying Web Sites with the Copy Web Site Tool"
You might be missing a key step in the process,
and reviewing those walkthroughs might point it out to you.
Juan T. Llibre
ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
==========================
"Steve Franks" <please@.postreplyhere.com> wrote in message
news:OeednTMpv_Zaj7XenZ2dnUVZ_s2dnZ2d@.co
mcast.com...
> Sorry about the confusion. Let me explain specifically what I'm trying to
do.
> Locally I'm using whatever the default settings are, as it relates to prec
ompiling.
> When I look at the property pages of my ASP.NET web application, and click
on the Build
> section, the revelant sections say "Before running startup page: Build Web
Site". And
> "Build solution action" section has the check box checked for "Build web s
ite as part of
> solution".
> That is how I like to run things because I prefer to know about any mishap
s I've made
> coding-wise before the page runs.
> Now over to production... I like the Copy Web function because it seems li
ke a
> convenient way from within VS.NET 2005 Beta 2 to easily have it sync the p
roduction site
> with changes as I make them in development.
> However recently I added a App_Code folder with a few utility classes I've
created. Now
> when I do the Copy Web the production site complains that the App_Code fol
der is not
> allowed.
> So my questions specifically are:
> 1) Is there a way where I can still use Copy Web in this scenario?
> 2) If not, how do I tell my local machine to not precompile and clear itse
lf from any
> precompiled files, so that when I do a copy web the remote site is not in
a precompiled
> mote? In other words, I assume my local machine has the precompiled files
that are
> being copied with Copy Web. So I do these get deleted, and how do I set t
hings set up
> locally so its no longer prcompiled, so that my production server will be
happy once I
> do a complete Copy Web to try and straighten things out?
> 3) If I have to resort to a FTP copy, files with what extension should get
copied
> specifically? Or perhaps its easier toi look at it the other way - which
file
> extensions need to be deleted from the production server so it does not se
e the web
> pages there as being "precompiled"?
> Thanks so much. I'm looking forward to your answer as I have been stuck o
n this for a
> few days. I really appreciate the help.
> Steve
> "Juan T. Llibre" <nomailreplies@.nowhere.com> wrote in message
> news:OvKJFZOuFHA.2072@.TK2MSFTNGP14.phx.gbl...
>
Thanks. I thnk you hit the nail on the head in that at one point a long
time ago I did use the Publish Web Site tool and probably did not check that
option.
It looks like I've resolved it by deleting the entire remote site and then
using Copy Web over again.
Steve
"Juan T. Llibre" <nomailreplies@.nowhere.com> wrote in message
news:%235MIaCTuFHA.3188@.TK2MSFTNGP14.phx.gbl...
> Hi, Steve.
> What this sounds like is that, at some point, the "Publish Web Site"
> tool was used instead of the "Copy Web" tool, and that the
> "Allow this precompiled site to be updatable" option was not selected.
> See : http://msdn2.microsoft.com/en-us/library/1y1404zt
> for a step-by-step guide to using the "Publish Web Site" tool.
> You can change the "Allow this site...to be updatable" option.
> You might also want to take a look at the "Copying a website" walkthrough:
> http://msdn2.microsoft.com/en-us/library/xay0wxbf
> and at : http://msdn2.microsoft.com/en-us/library/1cc82atw
> "Copying Web Sites with the Copy Web Site Tool"
> You might be missing a key step in the process,
> and reviewing those walkthroughs might point it out to you.
>
>
> Juan T. Llibre
> ASP.NET MVP
> ASP.NET FAQ : http://asp.net.do/faq/
> ==========================
> "Steve Franks" <please@.postreplyhere.com> wrote in message
> news:OeednTMpv_Zaj7XenZ2dnUVZ_s2dnZ2d@.co
mcast.com...
>
>

The directory /App_Code is not allowed because the application is precompiled

I'm using VS.NET 2005 Beta 2. I have a helper C# class I wrote that I placed
in my /App_Code directory. Everything runs fine locally. However when I
use the "Copy Web" function to upload the site to the production server, I
get the following error when trying to run the page on production:
"System.Web.HttpException: The directory '/App_Code' is not allowed
because the application is precompiled."

Anyone know this works fine locally but not on development? How can I
resolve this?

Also on a related note I read a lot about a new "\code" directory in ASP.NET
2.0. Am I correct to assume that at some point they changed this from \code
to \App_Code and these are the same thing?

SteveHi, Steve.

re:
> Am I correct to assume that at some point they changed this from \code to \App_Code and
> these are the same thing?

You're correct. In Beta 1 it was called /code.
In Beta 2, it was changed to /App_Code.

See http://msdn.microsoft.com/asp.net/w...eta2update.aspx
for a complete list of special directories.

re:
> "System.Web.HttpException: The directory '/App_Code' is not allowed because the
> application is precompiled."
> Anyone know this works fine locally but not on development? How can I resolve this?

You don't need to resolve it.

Because you're precompiling, everything that would go in the App_Code
directory is already compiled and doesn't need to be uploaded.

If you want to upload your source files into the
App_Code directory, don't precompile your application.

Juan T. Llibre
ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
==========================

"Steve Franks" <please@.postreplyhere.com> wrote in message
news:dfKdnTtsD5yXYLneRVn-jQ@.comcast.com...
> I'm using VS.NET 2005 Beta 2. I have a helper C# class I wrote that I placed in my
> /App_Code directory. Everything runs fine locally. However when I use the "Copy Web"
> function to upload the site to the production server, I get the following error when
> trying to run the page on production:
> "System.Web.HttpException: The directory '/App_Code' is not allowed because the
> application is precompiled."
> Anyone know this works fine locally but not on development? How can I resolve this?
> Also on a related note I read a lot about a new "\code" directory in ASP.NET 2.0. Am I
> correct to assume that at some point they changed this from \code to \App_Code and these
> are the same thing?
> Steve
> Because you're precompiling, everything that would go in the App_Code
> directory is already compiled and doesn't need to be uploaded.
> If you want to upload your source files into the
> App_Code directory, don't precompile your application.

I am not purposely precompiling my application. How can I prevent it from
precompiling?

Locally I just use VS.NET 2005 b2 to do the development and press F5 to run
it. Sometimes I press F6 to get a sanity check on whether I've screwed any
code up.

For production, I want the flexibility to be able to edit source on the
production server to make an update on the fly, so the precompiled approach
is not of interest.

My main goal is to just be able to easily synchronize the work I do at home
on the production server, and then get to work and easily update my local
dev copy of the web app to reflect the changes I've made at home by syncing
with the production server. Then I'll make changes at work, and when I get
home, I'll want to sync my home machine up with what's now on the production
server, and so forth. Currently I'm (trying) to use the Copy Web function
for this. Is that appropriate and/or is there a better way?

Thanks,

Steve
Juan,

Any ideas about what I posted below? Looking forward to your response. Than
you so much.

Steve,

"Steve Franks" <please@.postreplyhere.com> wrote in message
news:H_qdnYfD0ILDNrjeRVn-hQ@.comcast.com...
>> Because you're precompiling, everything that would go in the App_Code
>> directory is already compiled and doesn't need to be uploaded.
>>
>> If you want to upload your source files into the
>> App_Code directory, don't precompile your application.
>>
> I am not purposely precompiling my application. How can I prevent it from
> precompiling?
> Locally I just use VS.NET 2005 b2 to do the development and press F5 to
> run it. Sometimes I press F6 to get a sanity check on whether I've
> screwed any code up.
> For production, I want the flexibility to be able to edit source on the
> production server to make an update on the fly, so the precompiled
> approach is not of interest.
> My main goal is to just be able to easily synchronize the work I do at
> home on the production server, and then get to work and easily update my
> local dev copy of the web app to reflect the changes I've made at home by
> syncing with the production server. Then I'll make changes at work, and
> when I get home, I'll want to sync my home machine up with what's now on
> the production server, and so forth. Currently I'm (trying) to use the
> Copy Web function for this. Is that appropriate and/or is there a better
> way?
> Thanks,
> Steve
I would check your web project's properties under MSBuild.

-Brock
DevelopMentor
http://staff.develop.com/ballen

>> Because you're precompiling, everything that would go in the App_Code
>> directory is already compiled and doesn't need to be uploaded.
>>
>> If you want to upload your source files into the
>> App_Code directory, don't precompile your application.
> I am not purposely precompiling my application. How can I prevent it
> from precompiling?
> Locally I just use VS.NET 2005 b2 to do the development and press F5
> to run it. Sometimes I press F6 to get a sanity check on whether I've
> screwed any code up.
> For production, I want the flexibility to be able to edit source on
> the production server to make an update on the fly, so the precompiled
> approach is not of interest.
> My main goal is to just be able to easily synchronize the work I do at
> home on the production server, and then get to work and easily update
> my local dev copy of the web app to reflect the changes I've made at
> home by syncing with the production server. Then I'll make changes at
> work, and when I get home, I'll want to sync my home machine up with
> what's now on the production server, and so forth. Currently I'm
> (trying) to use the Copy Web function for this. Is that appropriate
> and/or is there a better way?
> Thanks,
> Steve
Well, there seems to be some sort of a conflict or design issue here with
this restriction.

I decided I'd just delete my App_Code directory from the remote site. I
figured this would be OK since its tellin gme the application is
precompiled. Yet then when I go to run a page it complains "The name
'myclass' does not exist in the current context". So if everything was
precompiled and no app_code directory is needed then what's the problem
here?

My preference is to precompile locally as I test and run my app, and then
when I publish to the remote server I want to publish all the files. I
can't seem to work around this. Any ideas?

Steve

"Brock Allen" <ballen@.NOSPAMdevelop.com> wrote in message
news:b8743b112290a8c7868466d649ee@.msnews.microsoft .com...
>I would check your web project's properties under MSBuild.
> -Brock
> DevelopMentor
> http://staff.develop.com/ballen
>>> Because you're precompiling, everything that would go in the App_Code
>>> directory is already compiled and doesn't need to be uploaded.
>>>
>>> If you want to upload your source files into the
>>> App_Code directory, don't precompile your application.
>> I am not purposely precompiling my application. How can I prevent it
>> from precompiling?
>>
>> Locally I just use VS.NET 2005 b2 to do the development and press F5
>> to run it. Sometimes I press F6 to get a sanity check on whether I've
>> screwed any code up.
>>
>> For production, I want the flexibility to be able to edit source on
>> the production server to make an update on the fly, so the precompiled
>> approach is not of interest.
>>
>> My main goal is to just be able to easily synchronize the work I do at
>> home on the production server, and then get to work and easily update
>> my local dev copy of the web app to reflect the changes I've made at
>> home by syncing with the production server. Then I'll make changes at
>> work, and when I get home, I'll want to sync my home machine up with
>> what's now on the production server, and so forth. Currently I'm
>> (trying) to use the Copy Web function for this. Is that appropriate
>> and/or is there a better way?
>>
>> Thanks,
>>
>> Steve
>>
re:
> My preference is to precompile locally as I test and run my app

I thought you had said you did *not* precompile.
There's a difference between "precompile" and "compile".

Which one are you doing ?

Have you tried to FTP your files instead of "publishing" them ?

Juan T. Llibre
ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
==========================

"Steve Franks" <please@.postreplyhere.com> wrote in message
news:gqqdnfBdIfGOFbrenZ2dnUVZ_s2dnZ2d@.comcast.com. ..
> Well, there seems to be some sort of a conflict or design issue here with this
> restriction.
> I decided I'd just delete my App_Code directory from the remote site. I figured this
> would be OK since its tellin gme the application is precompiled. Yet then when I go to
> run a page it complains "The name 'myclass' does not exist in the current context". So
> if everything was precompiled and no app_code directory is needed then what's the
> problem here?
> My preference is to precompile locally as I test and run my app, and then when I publish
> to the remote server I want to publish all the files. I can't seem to work around this.
> Any ideas?
> Steve

> "Brock Allen" <ballen@.NOSPAMdevelop.com> wrote in message
> news:b8743b112290a8c7868466d649ee@.msnews.microsoft .com...
>>I would check your web project's properties under MSBuild.
>>
>> -Brock
>> DevelopMentor
>> http://staff.develop.com/ballen
>>
>>>> Because you're precompiling, everything that would go in the App_Code
>>>> directory is already compiled and doesn't need to be uploaded.
>>>>
>>>> If you want to upload your source files into the
>>>> App_Code directory, don't precompile your application.
>>> I am not purposely precompiling my application. How can I prevent it
>>> from precompiling?
>>>
>>> Locally I just use VS.NET 2005 b2 to do the development and press F5
>>> to run it. Sometimes I press F6 to get a sanity check on whether I've
>>> screwed any code up.
>>>
>>> For production, I want the flexibility to be able to edit source on
>>> the production server to make an update on the fly, so the precompiled
>>> approach is not of interest.
>>>
>>> My main goal is to just be able to easily synchronize the work I do at
>>> home on the production server, and then get to work and easily update
>>> my local dev copy of the web app to reflect the changes I've made at
>>> home by syncing with the production server. Then I'll make changes at
>>> work, and when I get home, I'll want to sync my home machine up with
>>> what's now on the production server, and so forth. Currently I'm
>>> (trying) to use the Copy Web function for this. Is that appropriate
>>> and/or is there a better way?
>>>
>>> Thanks,
>>>
>>> Steve
Sorry about the confusion. Let me explain specifically what I'm trying to
do.

Locally I'm using whatever the default settings are, as it relates to
precompiling. When I look at the property pages of my ASP.NET web
application, and click on the Build section, the revelant sections say
"Before running startup page: Build Web Site". And "Build solution action"
section has the check box checked for "Build web site as part of solution".

That is how I like to run things because I prefer to know about any mishaps
I've made coding-wise before the page runs.

Now over to production... I like the Copy Web function because it seems like
a convenient way from within VS.NET 2005 Beta 2 to easily have it sync the
production site with changes as I make them in development.

However recently I added a App_Code folder with a few utility classes I've
created. Now when I do the Copy Web the production site complains that the
App_Code folder is not allowed.

So my questions specifically are:

1) Is there a way where I can still use Copy Web in this scenario?

2) If not, how do I tell my local machine to not precompile and clear itself
from any precompiled files, so that when I do a copy web the remote site is
not in a precompiled mote? In other words, I assume my local machine has
the precompiled files that are being copied with Copy Web. So I do these
get deleted, and how do I set things set up locally so its no longer
prcompiled, so that my production server will be happy once I do a complete
Copy Web to try and straighten things out?

3) If I have to resort to a FTP copy, files with what extension should get
copied specifically? Or perhaps its easier toi look at it the other way -
which file extensions need to be deleted from the production server so it
does not see the web pages there as being "precompiled"?

Thanks so much. I'm looking forward to your answer as I have been stuck on
this for a few days. I really appreciate the help.

Steve

"Juan T. Llibre" <nomailreplies@.nowhere.com> wrote in message
news:OvKJFZOuFHA.2072@.TK2MSFTNGP14.phx.gbl...
> re:
>> My preference is to precompile locally as I test and run my app
> I thought you had said you did *not* precompile.
> There's a difference between "precompile" and "compile".
> Which one are you doing ?
> Have you tried to FTP your files instead of "publishing" them ?
>
> Juan T. Llibre
> ASP.NET MVP
> ASP.NET FAQ : http://asp.net.do/faq/
> ==========================
> "Steve Franks" <please@.postreplyhere.com> wrote in message
> news:gqqdnfBdIfGOFbrenZ2dnUVZ_s2dnZ2d@.comcast.com. ..
>> Well, there seems to be some sort of a conflict or design issue here with
>> this restriction.
>>
>> I decided I'd just delete my App_Code directory from the remote site. I
>> figured this would be OK since its tellin gme the application is
>> precompiled. Yet then when I go to run a page it complains "The name
>> 'myclass' does not exist in the current context". So if everything was
>> precompiled and no app_code directory is needed then what's the problem
>> here?
>>
>> My preference is to precompile locally as I test and run my app, and then
>> when I publish to the remote server I want to publish all the files. I
>> can't seem to work around this. Any ideas?
>>
>> Steve
>> "Brock Allen" <ballen@.NOSPAMdevelop.com> wrote in message
>> news:b8743b112290a8c7868466d649ee@.msnews.microsoft .com...
>>>I would check your web project's properties under MSBuild.
>>>
>>> -Brock
>>> DevelopMentor
>>> http://staff.develop.com/ballen
>>>
>>>>> Because you're precompiling, everything that would go in the App_Code
>>>>> directory is already compiled and doesn't need to be uploaded.
>>>>>
>>>>> If you want to upload your source files into the
>>>>> App_Code directory, don't precompile your application.
>>>> I am not purposely precompiling my application. How can I prevent it
>>>> from precompiling?
>>>>
>>>> Locally I just use VS.NET 2005 b2 to do the development and press F5
>>>> to run it. Sometimes I press F6 to get a sanity check on whether I've
>>>> screwed any code up.
>>>>
>>>> For production, I want the flexibility to be able to edit source on
>>>> the production server to make an update on the fly, so the precompiled
>>>> approach is not of interest.
>>>>
>>>> My main goal is to just be able to easily synchronize the work I do at
>>>> home on the production server, and then get to work and easily update
>>>> my local dev copy of the web app to reflect the changes I've made at
>>>> home by syncing with the production server. Then I'll make changes at
>>>> work, and when I get home, I'll want to sync my home machine up with
>>>> what's now on the production server, and so forth. Currently I'm
>>>> (trying) to use the Copy Web function for this. Is that appropriate
>>>> and/or is there a better way?
>>>>
>>>> Thanks,
>>>>
>>>> Steve
Hi, Steve.

What this sounds like is that, at some point, the "Publish Web Site"
tool was used instead of the "Copy Web" tool, and that the
"Allow this precompiled site to be updatable" option was not selected.

See : http://msdn2.microsoft.com/en-us/library/1y1404zt
for a step-by-step guide to using the "Publish Web Site" tool.

You can change the "Allow this site...to be updatable" option.

You might also want to take a look at the "Copying a website" walkthrough:
http://msdn2.microsoft.com/en-us/library/xay0wxbf

and at : http://msdn2.microsoft.com/en-us/library/1cc82atw
"Copying Web Sites with the Copy Web Site Tool"

You might be missing a key step in the process,
and reviewing those walkthroughs might point it out to you.

Juan T. Llibre
ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
==========================

"Steve Franks" <please@.postreplyhere.com> wrote in message
news:OeednTMpv_Zaj7XenZ2dnUVZ_s2dnZ2d@.comcast.com. ..
> Sorry about the confusion. Let me explain specifically what I'm trying to do.
> Locally I'm using whatever the default settings are, as it relates to precompiling.
> When I look at the property pages of my ASP.NET web application, and click on the Build
> section, the revelant sections say "Before running startup page: Build Web Site". And
> "Build solution action" section has the check box checked for "Build web site as part of
> solution".
> That is how I like to run things because I prefer to know about any mishaps I've made
> coding-wise before the page runs.
> Now over to production... I like the Copy Web function because it seems like a
> convenient way from within VS.NET 2005 Beta 2 to easily have it sync the production site
> with changes as I make them in development.
> However recently I added a App_Code folder with a few utility classes I've created. Now
> when I do the Copy Web the production site complains that the App_Code folder is not
> allowed.
> So my questions specifically are:
> 1) Is there a way where I can still use Copy Web in this scenario?
> 2) If not, how do I tell my local machine to not precompile and clear itself from any
> precompiled files, so that when I do a copy web the remote site is not in a precompiled
> mote? In other words, I assume my local machine has the precompiled files that are
> being copied with Copy Web. So I do these get deleted, and how do I set things set up
> locally so its no longer prcompiled, so that my production server will be happy once I
> do a complete Copy Web to try and straighten things out?
> 3) If I have to resort to a FTP copy, files with what extension should get copied
> specifically? Or perhaps its easier toi look at it the other way - which file
> extensions need to be deleted from the production server so it does not see the web
> pages there as being "precompiled"?
> Thanks so much. I'm looking forward to your answer as I have been stuck on this for a
> few days. I really appreciate the help.
> Steve
> "Juan T. Llibre" <nomailreplies@.nowhere.com> wrote in message
> news:OvKJFZOuFHA.2072@.TK2MSFTNGP14.phx.gbl...
>> re:
>>> My preference is to precompile locally as I test and run my app
>>
>> I thought you had said you did *not* precompile.
>> There's a difference between "precompile" and "compile".
>>
>> Which one are you doing ?
>>
>> Have you tried to FTP your files instead of "publishing" them ?
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> ASP.NET FAQ : http://asp.net.do/faq/
>> ==========================
>>
>> "Steve Franks" <please@.postreplyhere.com> wrote in message
>> news:gqqdnfBdIfGOFbrenZ2dnUVZ_s2dnZ2d@.comcast.com. ..
>>> Well, there seems to be some sort of a conflict or design issue here with this
>>> restriction.
>>>
>>> I decided I'd just delete my App_Code directory from the remote site. I figured this
>>> would be OK since its tellin gme the application is precompiled. Yet then when I go
>>> to run a page it complains "The name 'myclass' does not exist in the current context".
>>> So if everything was precompiled and no app_code directory is needed then what's the
>>> problem here?
>>>
>>> My preference is to precompile locally as I test and run my app, and then when I
>>> publish to the remote server I want to publish all the files. I can't seem to work
>>> around this. Any ideas?
>>>
>>> Steve
>>
>>> "Brock Allen" <ballen@.NOSPAMdevelop.com> wrote in message
>>> news:b8743b112290a8c7868466d649ee@.msnews.microsoft .com...
>>>>I would check your web project's properties under MSBuild.
>>>>
>>>> -Brock
>>>> DevelopMentor
>>>> http://staff.develop.com/ballen
>>>>
>>>>>> Because you're precompiling, everything that would go in the App_Code
>>>>>> directory is already compiled and doesn't need to be uploaded.
>>>>>>
>>>>>> If you want to upload your source files into the
>>>>>> App_Code directory, don't precompile your application.
>>>>> I am not purposely precompiling my application. How can I prevent it
>>>>> from precompiling?
>>>>>
>>>>> Locally I just use VS.NET 2005 b2 to do the development and press F5
>>>>> to run it. Sometimes I press F6 to get a sanity check on whether I've
>>>>> screwed any code up.
>>>>>
>>>>> For production, I want the flexibility to be able to edit source on
>>>>> the production server to make an update on the fly, so the precompiled
>>>>> approach is not of interest.
>>>>>
>>>>> My main goal is to just be able to easily synchronize the work I do at
>>>>> home on the production server, and then get to work and easily update
>>>>> my local dev copy of the web app to reflect the changes I've made at
>>>>> home by syncing with the production server. Then I'll make changes at
>>>>> work, and when I get home, I'll want to sync my home machine up with
>>>>> what's now on the production server, and so forth. Currently I'm
>>>>> (trying) to use the Copy Web function for this. Is that appropriate
>>>>> and/or is there a better way?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Steve
>>
>>
Thanks. I thnk you hit the nail on the head in that at one point a long
time ago I did use the Publish Web Site tool and probably did not check that
option.

It looks like I've resolved it by deleting the entire remote site and then
using Copy Web over again.

Steve

"Juan T. Llibre" <nomailreplies@.nowhere.com> wrote in message
news:%235MIaCTuFHA.3188@.TK2MSFTNGP14.phx.gbl...
> Hi, Steve.
> What this sounds like is that, at some point, the "Publish Web Site"
> tool was used instead of the "Copy Web" tool, and that the
> "Allow this precompiled site to be updatable" option was not selected.
> See : http://msdn2.microsoft.com/en-us/library/1y1404zt
> for a step-by-step guide to using the "Publish Web Site" tool.
> You can change the "Allow this site...to be updatable" option.
> You might also want to take a look at the "Copying a website" walkthrough:
> http://msdn2.microsoft.com/en-us/library/xay0wxbf
> and at : http://msdn2.microsoft.com/en-us/library/1cc82atw
> "Copying Web Sites with the Copy Web Site Tool"
> You might be missing a key step in the process,
> and reviewing those walkthroughs might point it out to you.
>
>
> Juan T. Llibre
> ASP.NET MVP
> ASP.NET FAQ : http://asp.net.do/faq/
> ==========================
> "Steve Franks" <please@.postreplyhere.com> wrote in message
> news:OeednTMpv_Zaj7XenZ2dnUVZ_s2dnZ2d@.comcast.com. ..
>> Sorry about the confusion. Let me explain specifically what I'm trying
>> to do.
>>
>> Locally I'm using whatever the default settings are, as it relates to
>> precompiling.
>> When I look at the property pages of my ASP.NET web application, and
>> click on the Build
>> section, the revelant sections say "Before running startup page: Build
>> Web Site". And
>> "Build solution action" section has the check box checked for "Build web
>> site as part of
>> solution".
>>
>> That is how I like to run things because I prefer to know about any
>> mishaps I've made
>> coding-wise before the page runs.
>>
>> Now over to production... I like the Copy Web function because it seems
>> like a
>> convenient way from within VS.NET 2005 Beta 2 to easily have it sync the
>> production site
>> with changes as I make them in development.
>>
>> However recently I added a App_Code folder with a few utility classes
>> I've created. Now
>> when I do the Copy Web the production site complains that the App_Code
>> folder is not
>> allowed.
>>
>> So my questions specifically are:
>>
>> 1) Is there a way where I can still use Copy Web in this scenario?
>>
>> 2) If not, how do I tell my local machine to not precompile and clear
>> itself from any
>> precompiled files, so that when I do a copy web the remote site is not in
>> a precompiled
>> mote? In other words, I assume my local machine has the precompiled
>> files that are
>> being copied with Copy Web. So I do these get deleted, and how do I set
>> things set up
>> locally so its no longer prcompiled, so that my production server will be
>> happy once I
>> do a complete Copy Web to try and straighten things out?
>>
>> 3) If I have to resort to a FTP copy, files with what extension should
>> get copied
>> specifically? Or perhaps its easier toi look at it the other way - which
>> file
>> extensions need to be deleted from the production server so it does not
>> see the web
>> pages there as being "precompiled"?
>>
>> Thanks so much. I'm looking forward to your answer as I have been stuck
>> on this for a
>> few days. I really appreciate the help.
>>
>> Steve
>>
>> "Juan T. Llibre" <nomailreplies@.nowhere.com> wrote in message
>> news:OvKJFZOuFHA.2072@.TK2MSFTNGP14.phx.gbl...
>>> re:
>>>> My preference is to precompile locally as I test and run my app
>>>
>>> I thought you had said you did *not* precompile.
>>> There's a difference between "precompile" and "compile".
>>>
>>> Which one are you doing ?
>>>
>>> Have you tried to FTP your files instead of "publishing" them ?
>>>
>>>
>>>
>>> Juan T. Llibre
>>> ASP.NET MVP
>>> ASP.NET FAQ : http://asp.net.do/faq/
>>> ==========================
>>>
>>> "Steve Franks" <please@.postreplyhere.com> wrote in message
>>> news:gqqdnfBdIfGOFbrenZ2dnUVZ_s2dnZ2d@.comcast.com. ..
>>>> Well, there seems to be some sort of a conflict or design issue here
>>>> with this
>>>> restriction.
>>>>
>>>> I decided I'd just delete my App_Code directory from the remote site.
>>>> I figured this
>>>> would be OK since its tellin gme the application is precompiled. Yet
>>>> then when I go
>>>> to run a page it complains "The name 'myclass' does not exist in the
>>>> current context".
>>>> So if everything was precompiled and no app_code directory is needed
>>>> then what's the
>>>> problem here?
>>>>
>>>> My preference is to precompile locally as I test and run my app, and
>>>> then when I
>>>> publish to the remote server I want to publish all the files. I can't
>>>> seem to work
>>>> around this. Any ideas?
>>>>
>>>> Steve
>>>
>>>> "Brock Allen" <ballen@.NOSPAMdevelop.com> wrote in message
>>>> news:b8743b112290a8c7868466d649ee@.msnews.microsoft .com...
>>>>>I would check your web project's properties under MSBuild.
>>>>>
>>>>> -Brock
>>>>> DevelopMentor
>>>>> http://staff.develop.com/ballen
>>>>>
>>>>>>> Because you're precompiling, everything that would go in the
>>>>>>> App_Code
>>>>>>> directory is already compiled and doesn't need to be uploaded.
>>>>>>>
>>>>>>> If you want to upload your source files into the
>>>>>>> App_Code directory, don't precompile your application.
>>>>>> I am not purposely precompiling my application. How can I prevent it
>>>>>> from precompiling?
>>>>>>
>>>>>> Locally I just use VS.NET 2005 b2 to do the development and press F5
>>>>>> to run it. Sometimes I press F6 to get a sanity check on whether
>>>>>> I've
>>>>>> screwed any code up.
>>>>>>
>>>>>> For production, I want the flexibility to be able to edit source on
>>>>>> the production server to make an update on the fly, so the
>>>>>> precompiled
>>>>>> approach is not of interest.
>>>>>>
>>>>>> My main goal is to just be able to easily synchronize the work I do
>>>>>> at
>>>>>> home on the production server, and then get to work and easily update
>>>>>> my local dev copy of the web app to reflect the changes I've made at
>>>>>> home by syncing with the production server. Then I'll make changes
>>>>>> at
>>>>>> work, and when I get home, I'll want to sync my home machine up with
>>>>>> what's now on the production server, and so forth. Currently I'm
>>>>>> (trying) to use the Copy Web function for this. Is that appropriate
>>>>>> and/or is there a better way?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Steve
>>>
>>>
>>
>>
Thanks again Juan. On a different subject - since we are talking I was
wondering what approach you use to resolve the issue I posted about in a
posting called: "How to remove virtual path from root url of dev web server"
in this newsgroup on August 28. Likewise I have a similiar issue that I
posted about under the subject "Masterpage issue with relative links to
background images" on August 27.

It would be great if you could please share your thoughts on these
challenges.

Thank you,

Steve

"Juan T. Llibre" <nomailreplies@.nowhere.com> wrote in message
news:%235MIaCTuFHA.3188@.TK2MSFTNGP14.phx.gbl...
> Hi, Steve.
> What this sounds like is that, at some point, the "Publish Web Site"
> tool was used instead of the "Copy Web" tool, and that the
> "Allow this precompiled site to be updatable" option was not selected.
I have a local 03 server and i'm using IIS6, SQL 2005 and when go to run my aspx page i get "System.Web.HttpException: The directory '/App_Code/' is not allowed because the application is precompiled." but the remote server works fine. any ideas? thanks

Quote:

Originally Posted by Steve Franks

I'm using VS.NET 2005 Beta 2. I have a helper C# class I wrote that I placed
in my /App_Code directory. Everything runs fine locally. However when I
use the "Copy Web" function to upload the site to the production server, I
get the following error when trying to run the page on production:
"System.Web.HttpException: The directory '/App_Code' is not allowed
because the application is precompiled."

Anyone know this works fine locally but not on development? How can I
resolve this?

Also on a related note I read a lot about a new "\code" directory in ASP.NET
2.0. Am I correct to assume that at some point they changed this from \code
to \App_Code and these are the same thing?

Steve

THE FULL CLASS

hello, i'm kinda new to ASP.NET and web development

i've read that when i write behind-code for an .aspx file it's just a partial class

is there a way to read the content of the other partial class that contains the components' declarations?

Hey,

That part of the component is generated in your Temporary ASP.NET Files (under the windows\framework\<version>) folder for your application, which is where your ASP.NET pages are compiled. This was a feature meant to make it less of a coding effort. You can still access the objects in your code-behind page without those declarations.

I don't know if the web application project template does this or still includes the controls as in 1.1...

The hidden part of the partial class of web page in vs 2005

Hi all,

I want to see the hidden part of the partial class of web page.

I tried to right click on the class name and click on Find All References,
although visual studio 2005 got the other references, I was prohibited from
going there by a message box saying: The definition of the object is hidden.

Is there any way to see that hidden part?

Thank you.
BishoyThese files are just in time (JIT) compiled - so they don't exist until you
run the app.

The way I do this is:

-Load the application (in 2.0 each page is it's own assembly by default, so
browse to the page you wan to see)
-Open: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temp orary ASP.NET Files
-Open the folder that's the same name as web project
-Open whatever folder you find twice (not the _shadow). mine looked like
5365350a\c79f3d9b
-Then you'll see a bunch of dll's name something like
App_Web.asldjkasldj.dll
-Use Reflector (http://www.aisto.com/roeder/dotnet/) FREE, and open each one
up until you see your file. You should see an ASP and _ASP namespace.

Karl

--
http://www.openmymind.net/
http://www.codebetter.com/
"Bishoy George" <bishoy@.bishoy.comwrote in message
news:uRiIZZ5vGHA.5084@.TK2MSFTNGP04.phx.gbl...

Quote:

Originally Posted by

Hi all,
>
I want to see the hidden part of the partial class of web page.
>
I tried to right click on the class name and click on Find All References,
although visual studio 2005 got the other references, I was prohibited
from going there by a message box saying: The definition of the object is
hidden.
>
Is there any way to see that hidden part?
>
Thank you.
Bishoy
>