I did my MCAD sometime ago in 1.1, using the 305 manual. I've since moved up
to VS 2005. I've created perhaps a half dozen Dot Net 2.0 web applications.
(Click on the Create Project link within Recent Projects and Asp.Net Web
Applications.) Now I find out that my co-worker has been programming in a
different style. He's been using the File/New/Web Site menu item. If I ever
noticed that option, I've forgotten it.
Could someone briefly summarize the differences between web 'sites' and web
'applications'? (I thought all web sites were web applications.)
(My immediate motivation for posting here is that my coworker approached me
for help, since his website is giving 'AccessViolationException' errors, but
he swears that he has no unmanaged code that he knows of. It also looks to
me like the web site has no references at all, if that's even possible, so
I'm even more confused.)
7  1406 
VS 2005 introduced a new type of project called a Web Site Project. It
doesn't create a single dll for the entire site. Instead, code is seperated
out more, which leads to some annoying issues. For example, calling code in
folder b from a page in folder a probably won't work because the code in
folder b may not have compiled yet. To make code available throughout an
entire web site project it has to be in the App_Code directory. This new
project type annoyed a lot of people though so MS introduced the Web
Application Project back into VS first as an add-in, then as part of VS 2005
Service Pack 1. The Web Application Project is natively available in VS
2008.
The Web Application Project works pretty much the same way it did for the
1.x projects created by VS 2002 and 2003. The Web Site Project is more of an
interesting offshoot and does make it easier for people running VS Web
Developer Express to create a web site since they don't have to compile it
into a single-dll. Still, I prefer the single-dll method since it's easier
to pre-compile and if you need to call code that gets compiled into multiple
dlls you get the inter-dll communication hit.
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - Expression
"B. Chernick" <BC*******@discussions.microsoft.comwrote in message
news:7F**********************************@microsof t.com...
I did my MCAD sometime ago in 1.1, using the 305 manual. I've since moved
up
to VS 2005. I've created perhaps a half dozen Dot Net 2.0 web
applications.
(Click on the Create Project link within Recent Projects and Asp.Net Web
Applications.) Now I find out that my co-worker has been programming in a
different style. He's been using the File/New/Web Site menu item. If I
ever
noticed that option, I've forgotten it.
Could someone briefly summarize the differences between web 'sites' and
web
'applications'? (I thought all web sites were web applications.)
(My immediate motivation for posting here is that my coworker approached
me
for help, since his website is giving 'AccessViolationException' errors,
but
he swears that he has no unmanaged code that he knows of. It also looks
to
me like the web site has no references at all, if that's even possible, so
I'm even more confused.)
I prefer the same.
The time between VS2005 (no SP) and VS2005 SP1 seemed like an eternity.
That was one of those MS being too clever for its own good .. moments, IMHO.
"Mark Fitzpatrick" <ma******@fitzme.comwrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...
VS 2005 introduced a new type of project called a Web Site Project. It
doesn't create a single dll for the entire site. Instead, code is
seperated out more, which leads to some annoying issues. For example,
calling code in folder b from a page in folder a probably won't work
because the code in folder b may not have compiled yet. To make code
available throughout an entire web site project it has to be in the
App_Code directory. This new project type annoyed a lot of people though
so MS introduced the Web Application Project back into VS first as an
add-in, then as part of VS 2005 Service Pack 1. The Web Application
Project is natively available in VS 2008.
The Web Application Project works pretty much the same way it did for the
1.x projects created by VS 2002 and 2003. The Web Site Project is more of
an interesting offshoot and does make it easier for people running VS Web
Developer Express to create a web site since they don't have to compile it
into a single-dll. Still, I prefer the single-dll method since it's easier
to pre-compile and if you need to call code that gets compiled into
multiple dlls you get the inter-dll communication hit.
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - Expression
"B. Chernick" <BC*******@discussions.microsoft.comwrote in message
news:7F**********************************@microsof t.com...
>I did my MCAD sometime ago in 1.1, using the 305 manual. I've since
moved up
to VS 2005. I've created perhaps a half dozen Dot Net 2.0 web
applications.
(Click on the Create Project link within Recent Projects and Asp.Net Web
Applications.) Now I find out that my co-worker has been programming in
a
different style. He's been using the File/New/Web Site menu item. If I
ever
noticed that option, I've forgotten it.
Could someone briefly summarize the differences between web 'sites' and
web
'applications'? (I thought all web sites were web applications.)
(My immediate motivation for posting here is that my coworker approached
me
for help, since his website is giving 'AccessViolationException' errors,
but
he swears that he has no unmanaged code that he knows of. It also looks
to
me like the web site has no references at all, if that's even possible,
so
I'm even more confused.)
I'm getting the impression (correct me if I'm wrong) that Web application
projects are for professionals and web site projects are for amateurs.
Looks like I'll be sticking with web app projects. Thanks.
"Mark Fitzpatrick" wrote:
VS 2005 introduced a new type of project called a Web Site Project. It
doesn't create a single dll for the entire site. Instead, code is seperated
out more, which leads to some annoying issues. For example, calling code in
folder b from a page in folder a probably won't work because the code in
folder b may not have compiled yet. To make code available throughout an
entire web site project it has to be in the App_Code directory. This new
project type annoyed a lot of people though so MS introduced the Web
Application Project back into VS first as an add-in, then as part of VS 2005
Service Pack 1. The Web Application Project is natively available in VS
2008.
The Web Application Project works pretty much the same way it did for the
1.x projects created by VS 2002 and 2003. The Web Site Project is more of an
interesting offshoot and does make it easier for people running VS Web
Developer Express to create a web site since they don't have to compile it
into a single-dll. Still, I prefer the single-dll method since it's easier
to pre-compile and if you need to call code that gets compiled into multiple
dlls you get the inter-dll communication hit.
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - Expression
"B. Chernick" <BC*******@discussions.microsoft.comwrote in message
news:7F**********************************@microsof t.com...
I did my MCAD sometime ago in 1.1, using the 305 manual. I've since moved
up
to VS 2005. I've created perhaps a half dozen Dot Net 2.0 web
applications.
(Click on the Create Project link within Recent Projects and Asp.Net Web
Applications.) Now I find out that my co-worker has been programming in a
different style. He's been using the File/New/Web Site menu item. If I
ever
noticed that option, I've forgotten it.
Could someone briefly summarize the differences between web 'sites' and
web
'applications'? (I thought all web sites were web applications.)
(My immediate motivation for posting here is that my coworker approached
me
for help, since his website is giving 'AccessViolationException' errors,
but
he swears that he has no unmanaged code that he knows of. It also looks
to
me like the web site has no references at all, if that's even possible, so
I'm even more confused.)
That's the general impression most people had, but the Web Site Projects do
have advantages and weren't a bad idea, but most designers who are used to
the Web Application Projects find them more difficult and not worth the
effort. Still, there are a number of great open source apps that are written
with a Web Site Project since the core logic can still be put into an
external class project, avoiding some of the most annoying issues for this
project type.
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - Expression
"B. Chernick" <BC*******@discussions.microsoft.comwrote in message
news:8B**********************************@microsof t.com...
I'm getting the impression (correct me if I'm wrong) that Web application
projects are for professionals and web site projects are for amateurs.
Looks like I'll be sticking with web app projects. Thanks.
"Mark Fitzpatrick" wrote:
>VS 2005 introduced a new type of project called a Web Site Project. It
doesn't create a single dll for the entire site. Instead, code is
seperated
out more, which leads to some annoying issues. For example, calling code
in
folder b from a page in folder a probably won't work because the code in
folder b may not have compiled yet. To make code available throughout an
entire web site project it has to be in the App_Code directory. This new
project type annoyed a lot of people though so MS introduced the Web
Application Project back into VS first as an add-in, then as part of VS
2005
Service Pack 1. The Web Application Project is natively available in VS
2008.
The Web Application Project works pretty much the same way it did for the
1.x projects created by VS 2002 and 2003. The Web Site Project is more of
an
interesting offshoot and does make it easier for people running VS Web
Developer Express to create a web site since they don't have to compile
it
into a single-dll. Still, I prefer the single-dll method since it's
easier
to pre-compile and if you need to call code that gets compiled into
multiple
dlls you get the inter-dll communication hit.
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - Expression
"B. Chernick" <BC*******@discussions.microsoft.comwrote in message
news:7F**********************************@microso ft.com...
I did my MCAD sometime ago in 1.1, using the 305 manual. I've since
moved
up
to VS 2005. I've created perhaps a half dozen Dot Net 2.0 web
applications.
(Click on the Create Project link within Recent Projects and Asp.Net
Web
Applications.) Now I find out that my co-worker has been programming
in a
different style. He's been using the File/New/Web Site menu item. If
I
ever
noticed that option, I've forgotten it.
Could someone briefly summarize the differences between web 'sites' and
web
'applications'? (I thought all web sites were web applications.)
(My immediate motivation for posting here is that my coworker
approached
me
for help, since his website is giving 'AccessViolationException'
errors,
but
he swears that he has no unmanaged code that he knows of. It also
looks
to
me like the web site has no references at all, if that's even possible,
so
I'm even more confused.)
Hi,
In the end almost all the same things can be done with either of the models,
so in my opinion it is personal preference which one you use. I prefer WAP
but only because I've used to work with that kind of model since the first
days of .NET.
--
Teemu Keiski
AspInsider, ASP.NET MVP http://blogs.aspadvice.com/joteke http://teemukeiski.net
"B. Chernick" <BC*******@discussions.microsoft.comwrote in message
news:8B**********************************@microsof t.com...
I'm getting the impression (correct me if I'm wrong) that Web application
projects are for professionals and web site projects are for amateurs.
Looks like I'll be sticking with web app projects. Thanks.
"Mark Fitzpatrick" wrote:
>VS 2005 introduced a new type of project called a Web Site Project. It
doesn't create a single dll for the entire site. Instead, code is
seperated
out more, which leads to some annoying issues. For example, calling code
in
folder b from a page in folder a probably won't work because the code in
folder b may not have compiled yet. To make code available throughout an
entire web site project it has to be in the App_Code directory. This new
project type annoyed a lot of people though so MS introduced the Web
Application Project back into VS first as an add-in, then as part of VS
2005
Service Pack 1. The Web Application Project is natively available in VS
2008.
The Web Application Project works pretty much the same way it did for the
1.x projects created by VS 2002 and 2003. The Web Site Project is more of
an
interesting offshoot and does make it easier for people running VS Web
Developer Express to create a web site since they don't have to compile
it
into a single-dll. Still, I prefer the single-dll method since it's
easier
to pre-compile and if you need to call code that gets compiled into
multiple
dlls you get the inter-dll communication hit.
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - Expression
"B. Chernick" <BC*******@discussions.microsoft.comwrote in message
news:7F**********************************@microso ft.com...
I did my MCAD sometime ago in 1.1, using the 305 manual. I've since
moved
up
to VS 2005. I've created perhaps a half dozen Dot Net 2.0 web
applications.
(Click on the Create Project link within Recent Projects and Asp.Net
Web
Applications.) Now I find out that my co-worker has been programming
in a
different style. He's been using the File/New/Web Site menu item. If
I
ever
noticed that option, I've forgotten it.
Could someone briefly summarize the differences between web 'sites' and
web
'applications'? (I thought all web sites were web applications.)
(My immediate motivation for posting here is that my coworker
approached
me
for help, since his website is giving 'AccessViolationException'
errors,
but
he swears that he has no unmanaged code that he knows of. It also
looks
to
me like the web site has no references at all, if that's even possible,
so
I'm even more confused.)
Just one further note: So far (and I am still looking) I cannot find a
specific reference in the VS 2005 Help (Team edition) for the phrase 'Web
Site Project', either in the index or by search.
"Mark Fitzpatrick" wrote:
That's the general impression most people had, but the Web Site Projects do
have advantages and weren't a bad idea, but most designers who are used to
the Web Application Projects find them more difficult and not worth the
effort. Still, there are a number of great open source apps that are written
with a Web Site Project since the core logic can still be put into an
external class project, avoiding some of the most annoying issues for this
project type.
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - Expression
"B. Chernick" <BC*******@discussions.microsoft.comwrote in message
news:8B**********************************@microsof t.com...
I'm getting the impression (correct me if I'm wrong) that Web application
projects are for professionals and web site projects are for amateurs.
Looks like I'll be sticking with web app projects. Thanks.
"Mark Fitzpatrick" wrote:
VS 2005 introduced a new type of project called a Web Site Project. It
doesn't create a single dll for the entire site. Instead, code is
seperated
out more, which leads to some annoying issues. For example, calling code
in
folder b from a page in folder a probably won't work because the code in
folder b may not have compiled yet. To make code available throughout an
entire web site project it has to be in the App_Code directory. This new
project type annoyed a lot of people though so MS introduced the Web
Application Project back into VS first as an add-in, then as part of VS
2005
Service Pack 1. The Web Application Project is natively available in VS
2008.
The Web Application Project works pretty much the same way it did for the
1.x projects created by VS 2002 and 2003. The Web Site Project is more of
an
interesting offshoot and does make it easier for people running VS Web
Developer Express to create a web site since they don't have to compile
it
into a single-dll. Still, I prefer the single-dll method since it's
easier
to pre-compile and if you need to call code that gets compiled into
multiple
dlls you get the inter-dll communication hit.
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - Expression
"B. Chernick" <BC*******@discussions.microsoft.comwrote in message
news:7F**********************************@microsof t.com...
I did my MCAD sometime ago in 1.1, using the 305 manual. I've since
moved
up
to VS 2005. I've created perhaps a half dozen Dot Net 2.0 web
applications.
(Click on the Create Project link within Recent Projects and Asp.Net
Web
Applications.) Now I find out that my co-worker has been programming
in a
different style. He's been using the File/New/Web Site menu item. If
I
ever
noticed that option, I've forgotten it.
Could someone briefly summarize the differences between web 'sites' and
web
'applications'? (I thought all web sites were web applications.)
(My immediate motivation for posting here is that my coworker
approached
me
for help, since his website is giving 'AccessViolationException'
errors,
but
he swears that he has no unmanaged code that he knows of. It also
looks
to
me like the web site has no references at all, if that's even possible,
so
I'm even more confused.)
Let me append my previous post: Haven't found much yet in the official Help
but I did find these very interesting references: http://www.codersbarn.com/post/2008/...n-Project.aspx http://msdn.microsoft.com/en-us/libr...px#wapp_topic2
(So they dumped the 'traditional' web app in VS2005 and then brought it back
when developers complained?)
"Mark Fitzpatrick" wrote:
That's the general impression most people had, but the Web Site Projects do
have advantages and weren't a bad idea, but most designers who are used to
the Web Application Projects find them more difficult and not worth the
effort. Still, there are a number of great open source apps that are written
with a Web Site Project since the core logic can still be put into an
external class project, avoiding some of the most annoying issues for this
project type.
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - Expression
"B. Chernick" <BC*******@discussions.microsoft.comwrote in message
news:8B**********************************@microsof t.com...
I'm getting the impression (correct me if I'm wrong) that Web application
projects are for professionals and web site projects are for amateurs.
Looks like I'll be sticking with web app projects. Thanks.
"Mark Fitzpatrick" wrote:
VS 2005 introduced a new type of project called a Web Site Project. It
doesn't create a single dll for the entire site. Instead, code is
seperated
out more, which leads to some annoying issues. For example, calling code
in
folder b from a page in folder a probably won't work because the code in
folder b may not have compiled yet. To make code available throughout an
entire web site project it has to be in the App_Code directory. This new
project type annoyed a lot of people though so MS introduced the Web
Application Project back into VS first as an add-in, then as part of VS
2005
Service Pack 1. The Web Application Project is natively available in VS
2008.
The Web Application Project works pretty much the same way it did for the
1.x projects created by VS 2002 and 2003. The Web Site Project is more of
an
interesting offshoot and does make it easier for people running VS Web
Developer Express to create a web site since they don't have to compile
it
into a single-dll. Still, I prefer the single-dll method since it's
easier
to pre-compile and if you need to call code that gets compiled into
multiple
dlls you get the inter-dll communication hit.
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - Expression
"B. Chernick" <BC*******@discussions.microsoft.comwrote in message
news:7F**********************************@microsof t.com...
I did my MCAD sometime ago in 1.1, using the 305 manual. I've since
moved
up
to VS 2005. I've created perhaps a half dozen Dot Net 2.0 web
applications.
(Click on the Create Project link within Recent Projects and Asp.Net
Web
Applications.) Now I find out that my co-worker has been programming
in a
different style. He's been using the File/New/Web Site menu item. If
I
ever
noticed that option, I've forgotten it.
Could someone briefly summarize the differences between web 'sites' and
web
'applications'? (I thought all web sites were web applications.)
(My immediate motivation for posting here is that my coworker
approached
me
for help, since his website is giving 'AccessViolationException'
errors,
but
he swears that he has no unmanaged code that he knows of. It also
looks
to
me like the web site has no references at all, if that's even possible,
so
I'm even more confused.)
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics | |
by: Michael |
last post by:
Ive been programming for some time now, so i wanted to get into graphics, but
i wanted to see if I could make a Picture Viewer. I have no experience with
the picture control, ive tryed the MSDN...
|
by: IWP506 |
last post by:
Hello everyone. I have a header picture for my website with text on it
like "Home" "links" "about" etc. It's all 1 picture. I've seen
people's sites where they have 1 picture but somehow make...
|
by: Joel ELISE |
last post by:
Hi,
I'd like to know if it's possible to show a picture in a dialog box. I'm
programming in C language using WinAPI (for MS Windows).
If it's possible, please, let me know how. Everything I...
|
by: BPearson |
last post by:
Hello
I would like to have several sites share a single web.config file. To accomplish this, I would point the root of these sites to the same folder. Is there any reason why I might not want to...
|
by: jdn |
last post by:
I have a root application that has various sub-applications (subdirectories
set up as applications within IIS). All of the sub-applications rely on the
root application for profiles, membership,...
| | |
by: m.roello |
last post by:
In the book:
"Working with Microsoft Visual Studio 2005"
Craig Skibo wrote:
"The power of Visual Studio 2005 lies in its ability to empower users to
build, test, and debug powerful applications...
|
by: Alan Silver |
last post by:
Hello,
MSDN (amongst other places) is full of helpful advice on ways to do data
access, but they all seem geared to wards enterprise applications. Maybe
I'm in a minority, but I don't have those...
|
by: Mark Rae |
last post by:
Hi all,
I'm sure most of us round here have heard of Dino Esposito - *very* well
respected in our industry...
I was reading an article of his in this month's VSJ entitled "Architecture...
|
by: pbd22 |
last post by:
Hi.
This is just a disaster management question.
I am using XMLHTTP for the dynamic loading of content in a very
crucial area of my web site. Same as an IFrame, but using XMLHTTP and
a DIV. I...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
| | |
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and...
|
by: TSSRALBI |
last post by:
Hello
I'm a network technician in training and I need your help.
I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs.
The...
|
by: adsilva |
last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
| | |
by: 6302768590 |
last post by:
Hai team
i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated ...
| |
