S
Stephanie
I am not really understanding the difference. Why would one care about one
assembly per page, for example?
Thanks for your help!
assembly per page, for example?
Thanks for your help!
S
Stephanie
Mark said:
My google foo is weak. I did not get that first one. That is more helpful
than what I found. Thanks.
A
Author
This topic has been extensively discussed, from which I learned some
differences between these two models.
BTW, I think some people believe that the web application project
model is more professional than the website project model, claiming
that web application project model is for serious, senior web
application developers whereas the website project model is more of a
newbie, casual model. Is this really the case? Please share your two
cents. Thank you.
H
Hillbilly
The only significant difference between the two models is the apparent fact
that Web Application Projects are supported by Microsoft Team System to
enable assets to be shared and used in some way by others. Is that more
professional?
Did Rembrandt paint his masterpieces with a bunch of goofy managers "on the
team" sending email back and forth telling him what should be pink or blue?
Did Michelangelo sculpt the statue of David using a "team" of stone masons?
This topic has been extensively discussed, from which I learned some
differences between these two models.
BTW, I think some people believe that the web application project
model is more professional than the website project model, claiming
that web application project model is for serious, senior web
application developers whereas the website project model is more of a
newbie, casual model. Is this really the case? Please share your two
cents. Thank you.
that Web Application Projects are supported by Microsoft Team System to
enable assets to be shared and used in some way by others. Is that more
professional?
Did Rembrandt paint his masterpieces with a bunch of goofy managers "on the
team" sending email back and forth telling him what should be pink or blue?
Did Michelangelo sculpt the statue of David using a "team" of stone masons?
This topic has been extensively discussed, from which I learned some
differences between these two models.
BTW, I think some people believe that the web application project
model is more professional than the website project model, claiming
that web application project model is for serious, senior web
application developers whereas the website project model is more of a
newbie, casual model. Is this really the case? Please share your two
cents. Thank you.
A
Author
Hillbilly said:
In other word, they aren't that different in essence. I sorta agree.
I have no problem using either one of them, the only problem I have
with web application project is that I can't edit anything in debug
mode. Not sure if there is a workaround.
J
Juan T. Llibre
re:
!> In other word, they aren't that different in essence
The difference is in the way the pages are compiled.
With WAP, you can choose whether a single assembly, or more assemblies, is/are compiled.
re:
!> the only problem I have with web application project is that I can't edit anything in debug mode
That shouldn't be a problem with, or without, WAP.
Please review these common problems when debugging:
http://support.microsoft.com/kb/306172
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
=========================
!> In other word, they aren't that different in essence
The difference is in the way the pages are compiled.
With WAP, you can choose whether a single assembly, or more assemblies, is/are compiled.
re:
!> the only problem I have with web application project is that I can't edit anything in debug mode
That shouldn't be a problem with, or without, WAP.
Please review these common problems when debugging:
http://support.microsoft.com/kb/306172
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
=========================
C
Cowboy \(Gregory A Beamer\)
NO. They each have their pluses and minuses, but the religious wars go on to
figure out whether pepsi or coke is better. ;-)
The application model makes certain deployment scenarios easier. The web
site makes it easier to deploy a single page, depending on set up. The
application model, as mentioned by Hillbilly, also opens up certain
scenarios that are not available by default.
It appears web apps are the preferred method in Visual Studio 2010 (due out
when?) based on the CTP from October (beta out when?). They are also most
talked about in web "professional" blogs. You take that however you want.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Blog:
http://feeds.feedburner.com/GregoryBeamer
********************************************
| Think outside the box! |
********************************************
This topic has been extensively discussed, from which I learned some
differences between these two models.
BTW, I think some people believe that the web application project
model is more professional than the website project model, claiming
that web application project model is for serious, senior web
application developers whereas the website project model is more of a
newbie, casual model. Is this really the case? Please share your two
cents. Thank you.
figure out whether pepsi or coke is better. ;-)
The application model makes certain deployment scenarios easier. The web
site makes it easier to deploy a single page, depending on set up. The
application model, as mentioned by Hillbilly, also opens up certain
scenarios that are not available by default.
It appears web apps are the preferred method in Visual Studio 2010 (due out
when?) based on the CTP from October (beta out when?). They are also most
talked about in web "professional" blogs. You take that however you want.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Blog:
http://feeds.feedburner.com/GregoryBeamer
********************************************
| Think outside the box! |
********************************************
This topic has been extensively discussed, from which I learned some
differences between these two models.
BTW, I think some people believe that the web application project
model is more professional than the website project model, claiming
that web application project model is for serious, senior web
application developers whereas the website project model is more of a
newbie, casual model. Is this really the case? Please share your two
cents. Thank you.
A
Author
Thank you. I just took a look at the M$ support article you referred
to
They all talk about "Unable to start debugging on the web server".
But, I am wondering how to make editing possible while I debug a WAP
project, that is, edit without stopping the debugger.
J
Juan T. Llibre
re:
!> I am wondering how to make editing possible while I debug
!> a WAP project, that is, edit without stopping the debugger.
That is called "edit and continue"...and you must, specifically, enable it to be able to use it.
There's specific instructions/options here :
http://msdn.microsoft.com/en-us/library/6wzw9e0y.aspx
....but, basically, from the VS IDE, open the Tools menu and select Options.
In the Options dialog box, expand the Debugging folder,
select Edit and Continue and set the options you want.
Please read the security caution on that page before you enable remote debugging.
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
=========================
Thank you. I just took a look at the M$ support article you referred
to
They all talk about "Unable to start debugging on the web server".
But, I am wondering how to make editing possible while I debug a WAP
project, that is, edit without stopping the debugger.
!> I am wondering how to make editing possible while I debug
!> a WAP project, that is, edit without stopping the debugger.
That is called "edit and continue"...and you must, specifically, enable it to be able to use it.
There's specific instructions/options here :
http://msdn.microsoft.com/en-us/library/6wzw9e0y.aspx
....but, basically, from the VS IDE, open the Tools menu and select Options.
In the Options dialog box, expand the Debugging folder,
select Edit and Continue and set the options you want.
Please read the security caution on that page before you enable remote debugging.
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
=========================
Thank you. I just took a look at the M$ support article you referred
to
They all talk about "Unable to start debugging on the web server".
But, I am wondering how to make editing possible while I debug a WAP
project, that is, edit without stopping the debugger.
A
Author
Yeah, I know about "Edit and Continue", but it never works like what I
want.
1) If I keep Edit and Continue checked, in debugging mode, then if I
try to change the source code, I get an error popup which says:
"Changes are not allowed when the debugger has been attached to an
already running process or the code being debugged is optimized".
which I don't quite understand.
2) If I uncheck "Edit and Continue", in debugging mode, I can indeed
change the source code, but the change will not take effect unless you
stop the debugger and restart it, such "flexibility" really doesn't
make any sense.
I googled and see a lot of people having this problem, and so far I
haven't found any nice solution that lets me Edit and Continue like in
the Website project mode.
I am close to concluding that in the Web application project mode, the
kind of Edit and Continue like most people want just isn't possible.
I would be more than happy to be corrected.
J
Juan T. Llibre
re:
!> If I uncheck "Edit and Continue", in debugging mode, I can indeed change the source code,
!> but the change will not take effect unless you stop the debugger and restart it, such "flexibility"
!> really doesn't make any sense.
If you consider that there's no way for the debugger to acquire/recognize the new code
you inserted unless the code gets recompiled, that makes pretty good sense to me.
;-)
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
=========================
Yeah, I know about "Edit and Continue", but it never works like what I
want.
1) If I keep Edit and Continue checked, in debugging mode, then if I
try to change the source code, I get an error popup which says:
"Changes are not allowed when the debugger has been attached to an
already running process or the code being debugged is optimized".
which I don't quite understand.
2) If I uncheck "Edit and Continue", in debugging mode, I can indeed
change the source code, but the change will not take effect unless you
stop the debugger and restart it, such "flexibility" really doesn't
make any sense.
I googled and see a lot of people having this problem, and so far I
haven't found any nice solution that lets me Edit and Continue like in
the Website project mode.
I am close to concluding that in the Web application project mode, the
kind of Edit and Continue like most people want just isn't possible.
I would be more than happy to be corrected.
!> If I uncheck "Edit and Continue", in debugging mode, I can indeed change the source code,
!> but the change will not take effect unless you stop the debugger and restart it, such "flexibility"
!> really doesn't make any sense.
If you consider that there's no way for the debugger to acquire/recognize the new code
you inserted unless the code gets recompiled, that makes pretty good sense to me.
;-)
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
=========================
Yeah, I know about "Edit and Continue", but it never works like what I
want.
1) If I keep Edit and Continue checked, in debugging mode, then if I
try to change the source code, I get an error popup which says:
"Changes are not allowed when the debugger has been attached to an
already running process or the code being debugged is optimized".
which I don't quite understand.
2) If I uncheck "Edit and Continue", in debugging mode, I can indeed
change the source code, but the change will not take effect unless you
stop the debugger and restart it, such "flexibility" really doesn't
make any sense.
I googled and see a lot of people having this problem, and so far I
haven't found any nice solution that lets me Edit and Continue like in
the Website project mode.
I am close to concluding that in the Web application project mode, the
kind of Edit and Continue like most people want just isn't possible.
I would be more than happy to be corrected.