Can 2.0 use project references like in 1.1?

[BusEdge]

Hi all. I apologize if this has been asked/answered already, I couldn't
find any info. In 1.1, my standard web application structure includes a
front end website, and a management site (or administration site..
however you call it). The management site is a subfolder of the primary
site, say "/mgt" and it is a separate IIS application, so it has it's
own web.config and authentication scheme. Since both the mgt site and
the front end site use a lot of the same objects, I just create all my
object classes in the mgt site, and add a project reference from the
front end site to the mgt site so they can be shared. For the life of
me, I cannot figure out how to accomplish something similar in VS
2005/dotnet 2.0. Since there are no 'projects' anymore, I can't add a
'project' reference. And since there are no dll files anymore, I can't
just build my project and have a dll file plopped down somewhere so
that I can reference it. I have to publish the website to a folder
somewhere so that the dll gets created and then I can reference it.
This seems very cumbersome. All I want is for my object classes to be
available to both websites, and I want to be able to make changes
quickly to a class file and be able to access those changes without
having to publish the files so the dll gets generated. How do other
people do this?

Thanks in advance for any enlightenment!
Brandon

http://www.busedge.com

[Ken Cox [Microsoft MVP]]

Hi Brandon,

If you'd rather use the 1.1 project style with 2.0, you can now download the
Web Application Projects add-on:

"Web Application Projects provide a companion web project model that can be
used as an alternative to the built-in Web Site Project in Visual Studio
2005. This new model is ideal for web site developers who are converting a
Visual Studio .Net 2003 web project to Visual Studio 2005. (Released May 8,
2006)"

http://msdn.microsoft.com/asp.net/re...p/default.aspx

Ken
Microsoft MVP [ASP.NET]

"BusEdge" <sp*****@gmail.com> wrote in message
news:11**********************@m73g2000cwd.googlegr oups.com...

Hi all. I apologize if this has been asked/answered already, I couldn't
find any info. In 1.1, my standard web application structure includes a
front end website, and a management site (or administration site..
however you call it). The management site is a subfolder of the primary
site, say "/mgt" and it is a separate IIS application, so it has it's
own web.config and authentication scheme. Since both the mgt site and
the front end site use a lot of the same objects, I just create all my
object classes in the mgt site, and add a project reference from the
front end site to the mgt site so they can be shared. For the life of
me, I cannot figure out how to accomplish something similar in VS
2005/dotnet 2.0. Since there are no 'projects' anymore, I can't add a
'project' reference. And since there are no dll files anymore, I can't
just build my project and have a dll file plopped down somewhere so
that I can reference it. I have to publish the website to a folder
somewhere so that the dll gets created and then I can reference it.
This seems very cumbersome. All I want is for my object classes to be
available to both websites, and I want to be able to make changes
quickly to a class file and be able to access those changes without
having to publish the files so the dll gets generated. How do other
people do this?

Thanks in advance for any enlightenment!
Brandon

http://www.busedge.com

[BusEdge]

Ken,

Thanks so much. Although, I was hoping to get some insight as to the
new "VS 2005 way" of doing it, rather than downloading an add-in that
gives me the old functionality back. How _should_ this be done in the
new framework?

Thanks again,
Brandon
Ken Cox [Microsoft MVP] wrote:

Hi Brandon,

If you'd rather use the 1.1 project style with 2.0, you can now download the
Web Application Projects add-on:

"Web Application Projects provide a companion web project model that can be
used as an alternative to the built-in Web Site Project in Visual Studio
2005. This new model is ideal for web site developers who are converting a
Visual Studio .Net 2003 web project to Visual Studio 2005. (Released May 8,
2006)"

http://msdn.microsoft.com/asp.net/re...p/default.aspx

Ken
Microsoft MVP [ASP.NET]

"BusEdge" <sp*****@gmail.com> wrote in message
news:11**********************@m73g2000cwd.googlegr oups.com...

Hi all. I apologize if this has been asked/answered already, I couldn't
find any info. In 1.1, my standard web application structure includes a
front end website, and a management site (or administration site..
however you call it). The management site is a subfolder of the primary
site, say "/mgt" and it is a separate IIS application, so it has it's
own web.config and authentication scheme. Since both the mgt site and
the front end site use a lot of the same objects, I just create all my
object classes in the mgt site, and add a project reference from the
front end site to the mgt site so they can be shared. For the life of
me, I cannot figure out how to accomplish something similar in VS
2005/dotnet 2.0. Since there are no 'projects' anymore, I can't add a
'project' reference. And since there are no dll files anymore, I can't
just build my project and have a dll file plopped down somewhere so
that I can reference it. I have to publish the website to a folder
somewhere so that the dll gets created and then I can reference it.
This seems very cumbersome. All I want is for my object classes to be
available to both websites, and I want to be able to make changes
quickly to a class file and be able to access those changes without
having to publish the files so the dll gets generated. How do other
people do this?

Thanks in advance for any enlightenment!
Brandon

http://www.busedge.com

[Ken Cox [Microsoft MVP]]

Hi Brandon,

To me, the way it *should* be done is with that download. For some reason,
Microsoft decided not to implement it in the original version of VS 2005,
despite complaints during the beta.

Finally, they realized that they had taken something away that was very
useful and issued the fix.

http://msdn.microsoft.com/msdnmag/is...ExtremeASPNET/

I suppose the *right* way is to use aspnet_compiler.exe and a ton of
options:

http://msdn2.microsoft.com/en-us/library/ms229863.aspx

In the last couple of Web sites I've done, I used the single file model
where all the code was in the .aspx file (no codebehind). It makes it really
easy to update or add a page... just drop the new version into the directory
and you're done.

Ken
Microsoft MVP [ASP.NET]

"BusEdge" <sp*****@gmail.com> wrote in message
news:11**********************@r2g2000cwb.googlegro ups.com...

Ken,

Thanks so much. Although, I was hoping to get some insight as to the
new "VS 2005 way" of doing it, rather than downloading an add-in that
gives me the old functionality back. How _should_ this be done in the
new framework?

Thanks again,
Brandon
Ken Cox [Microsoft MVP] wrote:

Hi Brandon,

If you'd rather use the 1.1 project style with 2.0, you can now download
the
Web Application Projects add-on:

"Web Application Projects provide a companion web project model that can
be
used as an alternative to the built-in Web Site Project in Visual Studio
2005. This new model is ideal for web site developers who are converting
a
Visual Studio .Net 2003 web project to Visual Studio 2005. (Released May
8,
2006)"

http://msdn.microsoft.com/asp.net/re...p/default.aspx

Ken
Microsoft MVP [ASP.NET]

"BusEdge" <sp*****@gmail.com> wrote in message
news:11**********************@m73g2000cwd.googlegr oups.com...

> Hi all. I apologize if this has been asked/answered already, I couldn't
> find any info. In 1.1, my standard web application structure includes a
> front end website, and a management site (or administration site..
> however you call it). The management site is a subfolder of the primary
> site, say "/mgt" and it is a separate IIS application, so it has it's
> own web.config and authentication scheme. Since both the mgt site and
> the front end site use a lot of the same objects, I just create all my
> object classes in the mgt site, and add a project reference from the
> front end site to the mgt site so they can be shared. For the life of
> me, I cannot figure out how to accomplish something similar in VS
> 2005/dotnet 2.0. Since there are no 'projects' anymore, I can't add a
> 'project' reference. And since there are no dll files anymore, I can't
> just build my project and have a dll file plopped down somewhere so
> that I can reference it. I have to publish the website to a folder
> somewhere so that the dll gets created and then I can reference it.
> This seems very cumbersome. All I want is for my object classes to be
> available to both websites, and I want to be able to make changes
> quickly to a class file and be able to access those changes without
> having to publish the files so the dll gets generated. How do other
> people do this?
>
> Thanks in advance for any enlightenment!
> Brandon
>
> http://www.busedge.com
>

[BusEdge]

Ken, thanks so much. You have been most helpful.

Brandon
Ken Cox [Microsoft MVP] wrote:

Hi Brandon,

To me, the way it *should* be done is with that download. For some reason,
Microsoft decided not to implement it in the original version of VS 2005,
despite complaints during the beta.

Finally, they realized that they had taken something away that was very
useful and issued the fix.

http://msdn.microsoft.com/msdnmag/is...ExtremeASPNET/

I suppose the *right* way is to use aspnet_compiler.exe and a ton of
options:

http://msdn2.microsoft.com/en-us/library/ms229863.aspx

In the last couple of Web sites I've done, I used the single file model
where all the code was in the .aspx file (no codebehind). It makes it really
easy to update or add a page... just drop the new version into the directory
and you're done.

Ken
Microsoft MVP [ASP.NET]

"BusEdge" <sp*****@gmail.com> wrote in message
news:11**********************@r2g2000cwb.googlegro ups.com...

Ken,

Thanks so much. Although, I was hoping to get some insight as to the
new "VS 2005 way" of doing it, rather than downloading an add-in that
gives me the old functionality back. How _should_ this be done in the
new framework?

Thanks again,
Brandon
Ken Cox [Microsoft MVP] wrote:

Hi Brandon,

If you'd rather use the 1.1 project style with 2.0, you can now download
the
Web Application Projects add-on:

"Web Application Projects provide a companion web project model that can
be
used as an alternative to the built-in Web Site Project in Visual Studio
2005. This new model is ideal for web site developers who are converting
a
Visual Studio .Net 2003 web project to Visual Studio 2005. (Released May
8,
2006)"

http://msdn.microsoft.com/asp.net/re...p/default.aspx

Ken
Microsoft MVP [ASP.NET]

"BusEdge" <sp*****@gmail.com> wrote in message
news:11**********************@m73g2000cwd.googlegr oups.com...
> Hi all. I apologize if this has been asked/answered already, I couldn't
> find any info. In 1.1, my standard web application structure includes a
> front end website, and a management site (or administration site..
> however you call it). The management site is a subfolder of the primary
> site, say "/mgt" and it is a separate IIS application, so it has it's
> own web.config and authentication scheme. Since both the mgt site and
> the front end site use a lot of the same objects, I just create all my
> object classes in the mgt site, and add a project reference from the
> front end site to the mgt site so they can be shared. For the life of
> me, I cannot figure out how to accomplish something similar in VS
> 2005/dotnet 2.0. Since there are no 'projects' anymore, I can't add a
> 'project' reference. And since there are no dll files anymore, I can't
> just build my project and have a dll file plopped down somewhere so
> that I can reference it. I have to publish the website to a folder
> somewhere so that the dll gets created and then I can reference it.
> This seems very cumbersome. All I want is for my object classes to be
> available to both websites, and I want to be able to make changes
> quickly to a class file and be able to access those changes without
> having to publish the files so the dll gets generated. How do other
> people do this?
>
> Thanks in advance for any enlightenment!
> Brandon
>
> http://www.busedge.com
>