By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,239 Members | 1,493 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,239 IT Pros & Developers. It's quick & easy.

Is Visual Studio .NET ideal for ASP.NET + HTML site?

P: n/a
Hi All!

First of all I would like to say that VS.NET is one of the finest IDE I've
used in years. It really helps me code quickly. Workspace management using
auto hide windows, minimizing and maximizing of code segments, TO-DO list
management and automatic documentation (to name a few) are all superb. So I
really want to make the VS.NET IDE the primary development tool for me.

However, when it comes to developing ASP.NET websites, I have some
confusions. For instance, when I develop websites in ASP.NET, I want some of
them to be HTML and others to be ASPX. But the Solution Explorer only shows
ASPX files and other limited set of files. So I have to use Notepad or
Dreamweaver to edit the HTML and other files. This is really a pain when
rapidly developing ASPX websites.

Also it is hard to distinguish and manage the website files (ASPX and HTML
files) with VS.NET project files (vbproj, vbproj.webinfo and sln files to
name a few). In Classic ASP, all the development was done separately on VB6
or C++ and only the resulting DLL file is ported to the web directory so no
issues of mixing up project files and web files (but of course DLL hell is
there :P).

I must admit that my knowledge of VS.NET is only beginner level so that I'm
hoping someone to shed some light on this.

Many Thanks!
Don
Nov 20 '05 #1
Share this Question
Share on Google+
17 Replies


P: n/a
"Don Wash" <do*@wash.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...
However, when it comes to developing ASP.NET websites, I have some
confusions. For instance, when I develop websites in ASP.NET, I want some of them to be HTML and others to be ASPX. But the Solution Explorer only shows ASPX files and other limited set of files. So I have to use Notepad or
Dreamweaver to edit the HTML and other files. This is really a pain when
rapidly developing ASPX websites.


1) If you haven't added the HTML files to your project, they won't display
in the Solution Explorer unless you click the Show All Files button.

2) To add a new HTML file into an ASP.NET project, right-click the project
name, select Add, then Add HTML page.

3) To add an existing HTML file into an ASP.NET project, simply drag it into
the project from Windows Explorer, into a folder if you want.
Nov 20 '05 #2

P: n/a
<<<So I have to use Notepad or Dreamweaver to edit the HTML and other files.
This is really a pain when rapidly developing ASPX websites.>>

Don - I feel your pain!

I agree that VS.NET is superb and I use it for all of my code-behind work
and testing/debugging.

BUT

When I'm doing any serious development work I switch back and forth between
VS.NET and Dreamweaver. The reason for this is that when you are editing
HTML, VS.NET may decide to completely rearrange your HTML code (in your ASPX
or HTML files). It doesn't simply give you your original page layout but
with different HTML - it actaully gives you a brand new layout - and one you
probably won't like that in no way resembles your original layout (and no
way to undo the re arrangement).

This is a well-known and big-time issue with developers that Microsoft is
plenty aware of and they're promising to fix it in the next release of
Visual Studio - so there's no need to start yet another heated debate over
this issue here. In any case the first time it happens to you, you'll be
running for Dreamweaver or Notepad.

Separately, VS.NET is not designed nor intended to provide many of the site
management features packed into Dreamweaver.

Don't get rid of Dreamweaver quite yet.

-D

Nov 20 '05 #3

P: n/a
Hi Mark,

Thanks for the reply! I can now see the HTML files and other files. However,
how can I solve the problem that VS.NET project files are mixing with web
files? Obviously I don't want them to be uploaded to the web server.

Thanks again,
Don

"Mark Rae" <ma**@mark-N-O-S-P-A-M-rae.co.uk> wrote in message
news:ed**************@TK2MSFTNGP09.phx.gbl...
"Don Wash" <do*@wash.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...
However, when it comes to developing ASP.NET websites, I have some
confusions. For instance, when I develop websites in ASP.NET, I want
some of
them to be HTML and others to be ASPX. But the Solution Explorer only shows
ASPX files and other limited set of files. So I have to use Notepad or
Dreamweaver to edit the HTML and other files. This is really a pain when
rapidly developing ASPX websites.


1) If you haven't added the HTML files to your project, they won't display
in the Solution Explorer unless you click the Show All Files button.

2) To add a new HTML file into an ASP.NET project, right-click the project
name, select Add, then Add HTML page.

3) To add an existing HTML file into an ASP.NET project, simply drag it

into the project from Windows Explorer, into a folder if you want.

Nov 20 '05 #4

P: n/a
> This is a well-known and big-time issue with developers that Microsoft is
plenty aware of and they're promising to fix it in the next release of
Visual Studio - so there's no need to start yet another heated debate over
this issue here. In any case the first time it happens to you, you'll be
running for Dreamweaver or Notepad.


The "Auto Format" feature you speak of can be configured or even turned off
from within the Tools...Options dialogs.
Nov 20 '05 #5

P: n/a
> The "Auto Format" feature you speak of can be configured or even turned
off
from within the Tools...Options dialogs.

Really - where specifically is it? Can you tell me exactly how to turn it
off?

I'm especially interested being that there (1) I didn't find it there - and
I have looked carefully (2) online help doesn't mention it, and (3) are many
discussions in this very group mention how it's a big problem that Microsoft
is addressing. I have previously asked about it in this group as have many
others and the response has always been the same - "...wait for the 2005
version - until then, don't throw away your favorite HTML editor..."
Nov 20 '05 #6

P: n/a
"Doug" <Cl******@Livermore.com> wrote in news:OYnAbAVeEHA.3132
@TK2MSFTNGP11.phx.gbl:
Don't get rid of Dreamweaver quite yet.


I wholeheartedly agree. Dreamweaver kicks VS.NET's butt when it comes to
HTML editing.

--
Lucas Tam (RE********@rogers.com)
Please delete "REMOVE" from the e-mail address when replying.
http://members.ebay.com/aboutme/coolspot18/
Nov 20 '05 #7

P: n/a
(credit to Herfried, if I recall, for the link)

http://blogs.msdn.com/MikhailArkhipo...16/132886.aspx

"You do can switch formatting off in Tools | Options, but it will not solve
the underlying issue, it will only switch off pretty formatting."

Never tried turning it off myself, but sounds like it may still not help a
whole lot. Very aggravating.

Greg
"Doug" <Cl******@Livermore.com> wrote in message
news:%2***************@tk2msftngp13.phx.gbl...
The "Auto Format" feature you speak of can be configured or even turned off
from within the Tools...Options dialogs.

Really - where specifically is it? Can you tell me exactly how to turn it
off?

I'm especially interested being that there (1) I didn't find it there -

and I have looked carefully (2) online help doesn't mention it, and (3) are many discussions in this very group mention how it's a big problem that Microsoft is addressing. I have previously asked about it in this group as have many
others and the response has always been the same - "...wait for the 2005
version - until then, don't throw away your favorite HTML editor..."

Nov 20 '05 #8

P: n/a
Don,
Thanks for the reply! I can now see the HTML files and other files. However, how can I solve the problem that VS.NET project files are mixing with web
files? Obviously I don't want them to be uploaded to the web server.

Why do you upload your project files to the webserver?

Cor
Nov 20 '05 #9

P: n/a
Doug,

Visual Studio Net is in my opinion perfect for HTML editing, however not for
cut and past Website development. For that are better tools.

Just my opinion.

Cor
Nov 20 '05 #10

P: n/a
Greg,

For HTML editing I never use the designview part I go direct to "view in
browser", that is very fast and implements direct my javascript and css even
when I store that on a server on the other and of the world.

Cor
Nov 20 '05 #11

P: n/a
If you use VS.NET's built in Copy Project menu item (off of the Project
menu), it will copy ONLY the necessary files.

Greg
"Don Wash" <do*@wash.com> wrote in message
news:uz**************@tk2msftngp13.phx.gbl...
Hi Mark,

Thanks for the reply! I can now see the HTML files and other files. However, how can I solve the problem that VS.NET project files are mixing with web
files? Obviously I don't want them to be uploaded to the web server.

Thanks again,
Don

Nov 20 '05 #12

P: n/a
"Lucas Tam" <RE********@rogers.com> wrote in message
news:Xn***************************@140.99.99.130.. .
I wholeheartedly agree. Dreamweaver kicks VS.NET's butt when it comes to
HTML editing.


Are you listening to this, Microsoft? 'Cos if you're not, you should be! A
whole slew of your users think that part of one of your flagship development
tools is not as good as the opposition, which is what you hate more than
anything else, right...?

And I agree with them, BTW...:-)
Nov 20 '05 #13

P: n/a
Tools...Options

Text Editor section
HTML/XML section
Format sub-section
"Doug" <Cl******@Livermore.com> wrote in message
news:%2***************@tk2msftngp13.phx.gbl...
The "Auto Format" feature you speak of can be configured or even turned off
from within the Tools...Options dialogs.

Really - where specifically is it? Can you tell me exactly how to turn it
off?

I'm especially interested being that there (1) I didn't find it there -

and I have looked carefully (2) online help doesn't mention it, and (3) are many discussions in this very group mention how it's a big problem that Microsoft is addressing. I have previously asked about it in this group as have many
others and the response has always been the same - "...wait for the 2005
version - until then, don't throw away your favorite HTML editor..."

Nov 20 '05 #14

P: n/a
I've been hearing these complaints since FrontPage 97. And, I have to say
that many (not all) of the complaints come from folks who either don't know
how to configure the product to their liking (see my earlier reply in this
thread about turning off auto-formatting) or they don't understand how MS
intends their products to be used.

MS FrontPage is a wonderful HTML designer/editor with many site management
capabilities. VS .NET is more of a hard-core development environment and
not so much a site management tool.

You can use FP for low end HTML design if you like as well as site
management and VS .NET for the programming.

"Mark Rae" <ma**@mark-N-O-S-P-A-M-rae.co.uk> wrote in message
news:uM*************@TK2MSFTNGP09.phx.gbl...
"Lucas Tam" <RE********@rogers.com> wrote in message
news:Xn***************************@140.99.99.130.. .
I wholeheartedly agree. Dreamweaver kicks VS.NET's butt when it comes to
HTML editing.
Are you listening to this, Microsoft? 'Cos if you're not, you should be! A
whole slew of your users think that part of one of your flagship

development tools is not as good as the opposition, which is what you hate more than
anything else, right...?

And I agree with them, BTW...:-)

Nov 20 '05 #15

P: n/a
"Scott M." <s-***@nospam.nospam> wrote in message
news:eY*************@TK2MSFTNGP09.phx.gbl...
Tools...Options

Text Editor section
HTML/XML section
Format sub-section


Goes about 50% of the way to fixing the problem...
Nov 20 '05 #16

P: n/a
I'll say that it'll be more handy for Microsoft to make the
frontpage/dreamweaver plugin for VS.NET, if they think that way. So people
can choose to use the built in HTML editor of VS.NET or other HTML editor of
their choice much the same way as they can choose to use the built-in
browser or IE to view the ASP.NET pages.

Afterall "intergration" is what we ask an "Intergrated Development
Environment" for.

"Scott M." <s-***@nospam.nospam> bl
news:%2****************@TK2MSFTNGP11.phx.gbl g...
I've been hearing these complaints since FrontPage 97. And, I have to say
that many (not all) of the complaints come from folks who either don't know how to configure the product to their liking (see my earlier reply in this
thread about turning off auto-formatting) or they don't understand how MS
intends their products to be used.

MS FrontPage is a wonderful HTML designer/editor with many site management
capabilities. VS .NET is more of a hard-core development environment and
not so much a site management tool.

You can use FP for low end HTML design if you like as well as site
management and VS .NET for the programming.

"Mark Rae" <ma**@mark-N-O-S-P-A-M-rae.co.uk> wrote in message
news:uM*************@TK2MSFTNGP09.phx.gbl...
"Lucas Tam" <RE********@rogers.com> wrote in message
news:Xn***************************@140.99.99.130.. .
I wholeheartedly agree. Dreamweaver kicks VS.NET's butt when it comes to HTML editing.


Are you listening to this, Microsoft? 'Cos if you're not, you should be! A whole slew of your users think that part of one of your flagship

development
tools is not as good as the opposition, which is what you hate more than
anything else, right...?

And I agree with them, BTW...:-)


Nov 20 '05 #17

P: n/a
> And hence, the issue gets exacerbated. What I'm hearing is that MS
customers
are asking for a functionality that they have found in a competitor's
product.


Most folks just want an HTML editor that doesn't mess with *my* HTML. That
is why there are so many of us that still rely on Dreamweaver.

Microsoft, of course, could care less about well formed/standards-compliant
HTML. .net has a long way to go as does VS.net, and, certainly IE.

If you work in .net, there are only so many tools you are going to
use...most from MS, so there isn't necessarily a strong reason FOR them to
fix these things in any sort of expidited manner. Hopefully, Whidbey will be
an improvement.

-Darrel
Nov 21 '05 #18

This discussion thread is closed

Replies have been disabled for this discussion.