17
Replies
17
17
Replies
tsansone
AUTHOR
New Here
,
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.
tsansone
AUTHOR
New Here
,
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.
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.
tsansone
AUTHOR
New Here
,
Darrel,
Why integrate with SQL, Oracle, etc. then? Because they're there in a big way and it doesn't make sense to recreate the wheel. to some degree this is why Dreamweaver integrates with ASP.NET, because it's there in a big way and, given how Microsoft has bet the ranch on .NET and it's place in web development, it's not going anywhere but to gain market share. Thus, Dreamweaver's needs to integrate with it, like it does with various databases, so it can attract a larger market share of developers who see value working with its unique and powerful presentation development features. This is Adobe. It's primarily about presentation. It needs to own that space rather than waste its resources competing with a company that's steam rolling deeper into backend enterprise development. I think Adobe's board and senior management feel this way as well. One can see hints of it by looking at how their merging Macromedia into Adobe. Do you see Coldfusion being position like Dreamweaver and Flash? No, because Adobe knows it's space...presentation, i.e. the stuff one can see. So, when Dreamweaver expands resources to integrate ASP.NET they're doing the right thing. However, when the expand those resources and provide little to no guidance with regard to what it believes to be best practices around that integration, it reduces the ROI of those expanded resources and makes the market question its direction and commitment to that direction.
Why integrate with SQL, Oracle, etc. then? Because they're there in a big way and it doesn't make sense to recreate the wheel. to some degree this is why Dreamweaver integrates with ASP.NET, because it's there in a big way and, given how Microsoft has bet the ranch on .NET and it's place in web development, it's not going anywhere but to gain market share. Thus, Dreamweaver's needs to integrate with it, like it does with various databases, so it can attract a larger market share of developers who see value working with its unique and powerful presentation development features. This is Adobe. It's primarily about presentation. It needs to own that space rather than waste its resources competing with a company that's steam rolling deeper into backend enterprise development. I think Adobe's board and senior management feel this way as well. One can see hints of it by looking at how their merging Macromedia into Adobe. Do you see Coldfusion being position like Dreamweaver and Flash? No, because Adobe knows it's space...presentation, i.e. the stuff one can see. So, when Dreamweaver expands resources to integrate ASP.NET they're doing the right thing. However, when the expand those resources and provide little to no guidance with regard to what it believes to be best practices around that integration, it reduces the ROI of those expanded resources and makes the market question its direction and commitment to that direction.
AdChoices