We're going with complimentary product... Our design team are creating the .aspx/.ascx files with little or no C# implementation. These files are then integrated into the project build (VS.NET) and developers then hook everything up. Changes can still be made to the HTML in the .aspx files in Dreamweaver MX, without upsetting anything.
As an aside, we've found when you include a .aspx/.ascx file into a VS.NET project, it will create the class file for you (code-behind). I'm now thinking about knocking out an add-in to port the .aspx <script runat="server"></server> stuff into the .aspx.cs file... Best wishes S -----Original Message----- From: John [mailto:[EMAIL PROTECTED]] Sent: 01 May 2002 11:50 To: [EMAIL PROTECTED] Subject: [DOTNET] DreamWeaver MX - VS Replacement or a Complimentary Product...your thoughts. Hi all, For asp development I always used a combination of VI6 and Ultradev 4. Now VS.Net is out I love it, but the design view has a few snags (Not really errors just not the best design environment). This is where I think dreamweaver is really useful. Just been looking at Dreamweaver MX and it looks like this is possibly a good product to use standalone or with VS.Net (Depending on financial constraints). Anyway, just interested if anyone else uses a combination or if they have a preference (even though MX is still only in preview edition). Anyway here's a review: http://www.asp101.com/articles/john/dreamweavermx/default.asp Seeya John You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
