test topic --

Forum|Forum|19 years ago
May 7, 2006
8 replies
1104 views

This topic has been closed for replies.

Inspiring

Kevin

True but if you create the site in VS it will create the web.config file for
you.

--
Paul Whitham
Certified Dreamweaver MX2004 Professional
Adobe Community Expert - Dreamweaver

Valleybiz Internet Design
www.valleybiz.net

"Kevin Marshall" <kev@no-spam.webxel.com> wrote in message
news:eeuh1i$iqg$1@forums.macromedia.com...
> With VS.NET 2005 you don't need to "create" a new site, all you have to do
> is select open site and browse/select the root folder of the DW site.
>
> Thats how I work with both tools.
>
> --
> Kevin Marshall
> WebXeL.com Ltd
> http://www.webxel.com
>
> ASP.NET Dreamweaver Extensions
> http://www.webxel-dw.co.uk
>
> "Paul Whitham AdobeCommunityExpert" <design@valleybiz.net> wrote in
> message news:eesfcg$2si$1@forums.macromedia.com...
>> You have a couple of totally unnessecary steps in this process. To work
>> with DW & VS you do not need 2 local sites. Simple create the site in DW
>> as you have done in step one.
>>
>> Then in VS when you tell it to create a new site, you point the directory
>> to the location that DW has saved the files to. VS will tell you that the
>> location already has a site there, but it will give you an option of
>> saving to the location.
>>
>> That way you have one local site and one remote.
>>
>>
>>
>> --
>> Paul Whitham
>> Certified Dreamweaver MX2004 Professional
>> Adobe Community Expert - Dreamweaver
>>
>> Valleybiz Internet Design
>> www.valleybiz.net
>>
>> "ricky0110" <webforumsuser@macromedia.com> wrote in message
>> news:eerecn$ksn$1@forums.macromedia.com...
>>> Hi all,
>>>
>>> I have a quick and dirty solution and just developed a site using this
>>> setup.
>>> At the end of the day it's a basic 30 page site with registered users
>>> etc... so
>>> nothing too complicated. Not an ideal solution but it works and allows
>>> you to
>>> work with VB files and seperate the code. Definately not for the novice
>>> user as
>>> a lot of tweaking may bve required but studying the difference in the
>>> two
>>> programmes files does help understand.
>>>
>>> Stage 1
>>> The initial site has been developed in Dreamweaver 8. Templates, Library
>>> Items, Styles etc all created and a web server set up on a seperate
>>> machine.
>>> DIV layers have been set up and made editable.
>>>
>>> For each of the pages I created a vb file in Dreamweaver adding the
>>> Codefile &
>>> Inherits declarations.
>>>
>>> <%@ Page Language="VB" ContentType="text/html"
>>> ResponseEncoding="iso-8859-1" %>
>>>
>>> with
>>>
>>> <%@ Page Language="VB" AutoEventWireup="false"
>>> CodeFile="Default2.aspx.vb"
>>> Inherits="Default2" %>
>>>
>>> I understand that this may cause problems in the future if templates are
>>> being
>>> used as your changes to the page declarations will be removed but for
>>> smaller
>>> sites this can be resolved with a quick cut and paste or snippets.
>>>
>>> At this stage we have two copies of the site Local & Remote.
>>>
>>> Stage 2
>>> Create a new site in Visual Studio 2005 and place in the default
>>> location.
>>> This will create all the necessary config files, AppData etc.
>>>
>>> Set up the remote site as your Dreamweaver Local copy and pull in this
>>> site to
>>> Visual Studio. You will now be able to do all your coding & database
>>> work.
>>> Obviously you will have to be quite carefull not to upset any
>>> dreamweaver
>>> markup but shouldn't be too bad if your working with DIV layers...
>>>
>>> Stage 3
>>> Testing can be done at this stage using the internal webserver that
>>> Visual
>>> studio operates. For users accounts the ASP Configuration tool can be
>>> used and
>>> tested and Database connections set up etc. Once your are fully happy
>>> that all
>>> your coding has been done.
>>>
>>> Stage 4
>>> Synchronise the Visual studio Local copy with your Dreamweaver local
>>> site.
>>> then send this up to your webserver.
>>>
>>
>>
>
>

Newsgroup_User

Inspiring

With VS.NET 2005 you don't need to "create" a new site, all you have to do
is select open site and browse/select the root folder of the DW site.

Thats how I work with both tools.

--
Kevin Marshall
WebXeL.com Ltd
http://www.webxel.com

ASP.NET Dreamweaver Extensions
http://www.webxel-dw.co.uk

"Paul Whitham AdobeCommunityExpert" <design@valleybiz.net> wrote in message
news:eesfcg$2si$1@forums.macromedia.com...
> You have a couple of totally unnessecary steps in this process. To work
> with DW & VS you do not need 2 local sites. Simple create the site in DW
> as you have done in step one.
>
> Then in VS when you tell it to create a new site, you point the directory
> to the location that DW has saved the files to. VS will tell you that the
> location already has a site there, but it will give you an option of
> saving to the location.
>
> That way you have one local site and one remote.
>
>
>
> --
> Paul Whitham
> Certified Dreamweaver MX2004 Professional
> Adobe Community Expert - Dreamweaver
>
> Valleybiz Internet Design
> www.valleybiz.net
>
> "ricky0110" <webforumsuser@macromedia.com> wrote in message
> news:eerecn$ksn$1@forums.macromedia.com...
>> Hi all,
>>
>> I have a quick and dirty solution and just developed a site using this
>> setup.
>> At the end of the day it's a basic 30 page site with registered users
>> etc... so
>> nothing too complicated. Not an ideal solution but it works and allows
>> you to
>> work with VB files and seperate the code. Definately not for the novice
>> user as
>> a lot of tweaking may bve required but studying the difference in the two
>> programmes files does help understand.
>>
>> Stage 1
>> The initial site has been developed in Dreamweaver 8. Templates, Library
>> Items, Styles etc all created and a web server set up on a seperate
>> machine.
>> DIV layers have been set up and made editable.
>>
>> For each of the pages I created a vb file in Dreamweaver adding the
>> Codefile &
>> Inherits declarations.
>>
>> <%@ Page Language="VB" ContentType="text/html"
>> ResponseEncoding="iso-8859-1" %>
>>
>> with
>>
>> <%@ Page Language="VB" AutoEventWireup="false"
>> CodeFile="Default2.aspx.vb"
>> Inherits="Default2" %>
>>
>> I understand that this may cause problems in the future if templates are
>> being
>> used as your changes to the page declarations will be removed but for
>> smaller
>> sites this can be resolved with a quick cut and paste or snippets.
>>
>> At this stage we have two copies of the site Local & Remote.
>>
>> Stage 2
>> Create a new site in Visual Studio 2005 and place in the default
>> location.
>> This will create all the necessary config files, AppData etc.
>>
>> Set up the remote site as your Dreamweaver Local copy and pull in this
>> site to
>> Visual Studio. You will now be able to do all your coding & database
>> work.
>> Obviously you will have to be quite carefull not to upset any dreamweaver
>> markup but shouldn't be too bad if your working with DIV layers...
>>
>> Stage 3
>> Testing can be done at this stage using the internal webserver that
>> Visual
>> studio operates. For users accounts the ASP Configuration tool can be
>> used and
>> tested and Database connections set up etc. Once your are fully happy
>> that all
>> your coding has been done.
>>
>> Stage 4
>> Synchronise the Visual studio Local copy with your Dreamweaver local
>> site.
>> then send this up to your webserver.
>>
>
>

Newsgroup_User

Inspiring

You have a couple of totally unnessecary steps in this process. To work with
DW & VS you do not need 2 local sites. Simple create the site in DW as you
have done in step one.

Then in VS when you tell it to create a new site, you point the directory to
the location that DW has saved the files to. VS will tell you that the
location already has a site there, but it will give you an option of saving
to the location.

That way you have one local site and one remote.

--
Paul Whitham
Certified Dreamweaver MX2004 Professional
Adobe Community Expert - Dreamweaver

Valleybiz Internet Design
www.valleybiz.net

"ricky0110" <webforumsuser@macromedia.com> wrote in message
news:eerecn$ksn$1@forums.macromedia.com...
> Hi all,
>
> I have a quick and dirty solution and just developed a site using this
> setup.
> At the end of the day it's a basic 30 page site with registered users
> etc... so
> nothing too complicated. Not an ideal solution but it works and allows you
> to
> work with VB files and seperate the code. Definately not for the novice
> user as
> a lot of tweaking may bve required but studying the difference in the two
> programmes files does help understand.
>
> Stage 1
> The initial site has been developed in Dreamweaver 8. Templates, Library
> Items, Styles etc all created and a web server set up on a seperate
> machine.
> DIV layers have been set up and made editable.
>
> For each of the pages I created a vb file in Dreamweaver adding the
> Codefile &
> Inherits declarations.
>
> <%@ Page Language="VB" ContentType="text/html"
> ResponseEncoding="iso-8859-1" %>
>
> with
>
> <%@ Page Language="VB" AutoEventWireup="false" CodeFile="Default2.aspx.vb"
> Inherits="Default2" %>
>
> I understand that this may cause problems in the future if templates are
> being
> used as your changes to the page declarations will be removed but for
> smaller
> sites this can be resolved with a quick cut and paste or snippets.
>
> At this stage we have two copies of the site Local & Remote.
>
> Stage 2
> Create a new site in Visual Studio 2005 and place in the default location.
> This will create all the necessary config files, AppData etc.
>
> Set up the remote site as your Dreamweaver Local copy and pull in this
> site to
> Visual Studio. You will now be able to do all your coding & database work.
> Obviously you will have to be quite carefull not to upset any dreamweaver
> markup but shouldn't be too bad if your working with DIV layers...
>
> Stage 3
> Testing can be done at this stage using the internal webserver that Visual
> studio operates. For users accounts the ASP Configuration tool can be used
> and
> tested and Database connections set up etc. Once your are fully happy that
> all
> your coding has been done.
>
> Stage 4
> Synchronise the Visual studio Local copy with your Dreamweaver local site.
> then send this up to your webserver.
>

Anonymous

Hi all,

I have a quick and dirty solution and just developed a site using this setup. At the end of the day it's a basic 30 page site with registered users etc... so nothing too complicated. Not an ideal solution but it works and allows you to work with VB files and seperate the code. Definately not for the novice user as a lot of tweaking may bve required but studying the difference in the two programmes files does help understand.

Stage 1
The initial site has been developed in Dreamweaver 8. Templates, Library Items, Styles etc all created and a web server set up on a seperate machine. DIV layers have been set up and made editable.

For each of the pages I created a vb file in Dreamweaver adding the Codefile & Inherits declarations.

<%@ Page Language="VB" ContentType="text/html" ResponseEncoding="iso-8859-1" %>

with

<%@ Page Language="VB" AutoEventWireup="false" CodeFile="Default2.aspx.vb" Inherits="Default2" %>

I understand that this may cause problems in the future if templates are being used as your changes to the page declarations will be removed but for smaller sites this can be resolved with a quick cut and paste or snippets.

At this stage we have two copies of the site Local & Remote.

Stage 2
Create a new site in Visual Studio 2005 and place in the default location. This will create all the necessary config files, AppData etc.

Set up the remote site as your Dreamweaver Local copy and pull in this site to Visual Studio. You will now be able to do all your coding & database work. Obviously you will have to be quite carefull not to upset any dreamweaver markup but shouldn't be too bad if your working with DIV layers...

Stage 3
Testing can be done at this stage using the internal webserver that Visual studio operates. For users accounts the ASP Configuration tool can be used and tested and Database connections set up etc. Once your are fully happy that all your coding has been done.

Stage 4
Synchronise the Visual studio Local copy with your Dreamweaver local site. then send this up to your webserver.

Anonymous

Hi,

I'm in the same boat as you. VS2005 is far better for designing the presentation layer than previous versions but Dreamweaver is still preferred by myself. I have just created an aspx site in Dreamweaver (Templates, Library items etc...) and imported into Visual Studio 2005 no problem.

The only difference I can see "so far" is that the aspx files when imported do not give you the option of splitting the code into a seperate vb file. For example when a new webform is created in VS2005 you have a checkbox automatically checked that splits say webform.aspx into webform.aspx & webform.aspx .vb

This is an annoyance as I would prefer to do the coding in the vb file. I thought this might just be a case of right clicking the file and changing preferences but I have had no response from the Microsoft user groupos on this question. If anyone can shed light on this issue I also would be grateful.

tsansoneAuthor

Participating Frequently

Ricky,
I noticed that too, among other things. This is what led me to look for a "best-practices" white paper by Adobe on how best to leverage the two IDE's with ASP.NET. I only see this issue getting larger as ASP.NET continues to add more sophisticated presentation features, such as Master Pages, Themes, etc. It just seems to me that if Dreamweaver is going to attempt to incorporate ASP.NET, then it should provide "best-practices" documentation on when and where Dreamweaver helps you and hurts you when developing ASP.NET applications. Otherwise, I'm afraid the end result will be generally Dreamweaver users either under-utilizing ASP.NET capabilities or, worse, stereotyped for creating non-enterprise level ASP.NET applications. Obviously, someone somewhere in Adobe is making strategic business decisions about the incorporation of ASP.NET in Dreamweaver. Well...then step up and be clear on where Dreamweaver ends and VS.NET begins, and provide best practice guidance to highlight and assure Dreamweaver's value-add into the development process through the spectrum of Mom-and-Pop apps to Enterprise caliber apps.

Newsgroup_User

Inspiring

Tom,

One known problem is with editing Template Instance (derived from a
Template) pages in Visual Studio 2003 and earlier (not sure if this was
fixed in VS 2005). VS takes the liberty of moving the Template markers
(which it sees simply as HTML Comments) from outside of <head> to inside
<head>. This breaks the page for DW MX 2004 and earlier. You'll need to
manually edit the page in "another" editor (not sure if it can be fixed
in VS) to fix this.

As far as I know, this has been fixed in DW8.

Hope this helps,
Randy

> I love Dreamweaver 8's ability to design presentation tier, but I find it lacks
> the robustness of Visual Studio 2005 for server-side ASP.NET coding. Frankly, I
> think the best of both worlds would be to first layout the presentation in
> Dreamweaver then migrate those file over into a VS.NET solution. Has anyone
> done this? Or, does anyone know of any white papers discussing this migration?

tsansoneAuthor

Participating Frequently

Randy,
Thanks for the head's up. That's exactly what I mean, those quirks one should be aware about before planning a dual IDE development process. I'm surprised how little documentation there is on the subject. One would think that Adobe/Macromedia would have a white paper showing how to best leverage their product with VS.NET, since, short of small web apps, it would be naive to expect to compete against it on ASP.NET server-side development but powerful to provide it a leg up with presentation.
Tom

Newsgroup_User

Inspiring

> Has anyone
> done this? Or, does anyone know of any white papers discussing this
> migration?
> Thx, Tom

There's really nothing to 'migrate'. Just edit the aspx page in whichever
editor you want to at the time.

-Darrel

tsansoneAuthor

Participating Frequently

Well, you'll have to bear with me since I'm new to Dreamweaver; however, I do believe there are some "do's-and-don'ts" if one would like to use both IDEs in a development process. Some that I'm seeing right away are adding the Bin folder, manually adding to the webconfig file, planning for ASP.NET code behind files, etc.
I've only been working with Dreamweaver for about a week now, but I'm sure I'll be discovering more little quirks and planning that should be apart of an optimal "Design-to-Code" workflow using Dreamweaver 8 and VS.NET 2005, specifically. My question is whether anyone has laid out the issues and the process to handle them. The first reply, by Paul Whitham, came close, but unfortunately the referenced material ran across the surface, rather than explicitly pointing out the quirks and suggesting how far to go in Dreamweaver without going too far into what should be best left the domain of VS.NET.

Newsgroup_User

Inspiring

What you are suggesting is the recommended method unless you want to deploy
master pages because then you are better to work solely in VS. Julian
Roberts has an article at www.charon.co.uk. This was written for the
previous version of VS but most of it is still relevant.

--
Paul Whitham
Certified Dreamweaver MX2004 Professional
Adobe Community Expert - Dreamweaver

Valleybiz Internet Design
www.valleybiz.net

"tsansone" <webforumsuser@macromedia.com> wrote in message
news:e3m1d7$d8d$1@forums.macromedia.com...
>I love Dreamweaver 8's ability to design presentation tier, but I find it
>lacks
> the robustness of Visual Studio 2005 for server-side ASP.NET coding.
> Frankly, I
> think the best of both worlds would be to first layout the presentation in
> Dreamweaver then migrate those file over into a VS.NET solution. Has
> anyone
> done this? Or, does anyone know of any white papers discussing this
> migration?
> Thx, Tom
>

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded