Posted By: Minh | Jul 29th @ 6:30 AM
page 1 of 1
Comments: 8 | Views: 829
Minh
Minh
WOOH! WOOH!

I'm starting my first serious ASP.NET 2.0 project and found that it's not creating a {Site}\bin\MyProj.dll file and that it requires the .cs files...

 

This is cool and all, but I'm not comfortable putting source code out there...

 

I read that there's a pre-compile util, but that needs to be ran on the production server... and you still need the .cs files...

 

Is there a way to build the ASP.NET 2.0 project like how VS2003 did it?

 

With the bin DLL?

blowdart
blowdart
Peek-a-boo

Ah did you do Create > New Web Site?

 

Throw that away. Do Create > New Solution > ASP.NET Website. Then, when you compile, you get a lovely single DLL.

W3bbo
W3bbo
The Master of Baiters

I think you mean "ASP.NET Web Application".

stevo_
stevo_
Human after all

I think it was aimed at classic asp style building with the runtime compilation model and various other concepts that in reality made website projects terrible.

W3bbo
W3bbo
The Master of Baiters

I thought it was more to do with lowering the barrier-to-entry (with "Web Developer Express"); except it made life harder for everyone else. I remember having to wait 6 months or so before ScottGu released the official Web Applications add-on for VS2005. I think they were trying to pitch VS as a competitor to Dreamweaver, even though (IMO) that's like Mercedes-Benz trying to compete with Skoda.

 

And I note that VS2008 still lacks FPSE support for Web Applications that VS2003 had, yet uses it fine for Web Sites.

stevo_
stevo_
Human after all

Yes well thats what I meant by being more like classic asp, the potential audience would be people who did php and asp etc, and making it as close to what they knew was a good way to lower that barrier to entrry.

figuerres
figuerres
???

just fyi:  if you use "new web site" you can chose build | publish and that also makes dlls for deployment.

page 1 of 1
Comments: 8 | Views: 829
Microsoft Communities