I don't know how this thing got released...
In trial mode if you open a web site from a directory and then double click on a page (or anything else you can do to try and get the damn page to open) the page won't open on the first run of the program. It's only the second time you run the program that
it works.
And even then, all absolutely pathed files (i.e. /images/bg.gif) without the HTTP part and not relative don't display at all.
It also freaks out about master pages that it can't find for the same reason (absolute pathing: /masters/masterpage.master) that work just fine thank you if I load the same web site in VS.NET 2005
How did this get out the door when it doesn't even load the most basic of VS.net 2005 sites and won't open a page for editing the first time you open the application? The average user, finding that they can't open pages to edit, gives up, closes the application
and uninstalls it immediately.
*head shake*
-
-
Oh I'm glad you said it! It definitly has some great features like support for ASP.NET, but otherwise I miss FrontPage! FrontPage 2003 feels much more polished that Expression Web does. Like you mentioned, Expression Web does not always do what you tell it to do... or it does it in seemingly random ways. And it's very common to get lockups when working with pages either locally or off the server. If I could find a way to get FrontPage to work correctly on Vista I would use that in a heartbeat, but as it stands Vista breaks basic functions in FrontPage that makes it unusable.
With FrontPage, I would always turn to it when needing to design something for Visual Studio since it's design surface was way better than VS. But now with Expression Web, they are about the same to me. I have so many problems designing in Expression Web that I end up just doing the design in Visual Studio. Now that's sad! -
Is it me, have I missed it, or is there no method of tying it into source control?
-
numedia wrote:Oh I'm glad you said it! It definitly has some great features like support for ASP.NET, but otherwise I miss FrontPage! FrontPage 2003 feels much more polished that Expression Web does. Like you mentioned, Expression Web does not always do what you tell it to do... or it does it in seemingly random ways. And it's very common to get lockups when working with pages either locally or off the server. If I could find a way to get FrontPage to work correctly on Vista I would use that in a heartbeat, but as it stands Vista breaks basic functions in FrontPage that makes it unusable.
With FrontPage, I would always turn to it when needing to design something for Visual Studio since it's design surface was way better than VS. But now with Expression Web, they are about the same to me. I have so many problems designing in Expression Web that I end up just doing the design in Visual Studio. Now that's sad!
Have you tried DreamWeaver? Its template system and CSS support is amazing. It also can automatically get database informations from the remote server and lets you create queries and insert/delete forms just with a few clicks. -
blowdart wrote:Is it me, have I missed it, or is there no method of tying it into source control?
You can tie into source control via the basic FrontPage or SharePoint check in/out. Otherwise, I check out a page using Visual Studio, then edit that page in Expression Web, then check back in with VS. -
cescotto wrote:
Have you tried DreamWeaver? Its template system and CSS support is amazing. It also can automatically get database informations from the remote server and lets you create queries and insert/delete forms just with a few clicks.
Used to use Dreamweaver, but couldn't stand the UI. It took took long to get things done and at the time there was no support for the full ASP.NET lineup. Perhaps that's changed now. -
Is Expression Web for the vs.net developer? I had thought it was more for the hobbyist dev.
-
cescotto wrote:

numedia wrote:Oh I'm glad you said it! It definitly has some great features like support for ASP.NET, but otherwise I miss FrontPage! FrontPage 2003 feels much more polished that Expression Web does. Like you mentioned, Expression Web does not always do what you tell it to do... or it does it in seemingly random ways. And it's very common to get lockups when working with pages either locally or off the server. If I could find a way to get FrontPage to work correctly on Vista I would use that in a heartbeat, but as it stands Vista breaks basic functions in FrontPage that makes it unusable.
With FrontPage, I would always turn to it when needing to design something for Visual Studio since it's design surface was way better than VS. But now with Expression Web, they are about the same to me. I have so many problems designing in Expression Web that I end up just doing the design in Visual Studio. Now that's sad!
Have you tried DreamWeaver? Its template system and CSS support is amazing. It also can automatically get database informations from the remote server and lets you create queries and insert/delete forms just with a few clicks.
Dreamweaver's "Server Behaviours" only work if you don't dare modify the generated VBS, and after reviewing the code they're highly insecure. They're vulnerable to SQL Injection, for example, and deliberately obfuscated with bizarre variable identifiers.
I don't recommend Dreamweaver for anything besides learning the basics, anything hardcore can be done with more suitable applications (Komodo and VisualStudio, for example)
-
Sadly we are seeing alot of half-baked products that Microsoft is trying to push out the door way too fast. Just look at XNA... Waay too fast.
-
Chadk wrote:Sadly we are seeing alot of half-baked products that Microsoft is trying to push out the door way too fast. Just look at XNA... Waay too fast.
Well, this is the new MS with the more frequent release cycles. And, um, we've all been asking for this.
-
numedia wrote:

blowdart wrote:Is it me, have I missed it, or is there no method of tying it into source control?
You can tie into source control via the basic FrontPage or SharePoint check in/out. Otherwise, I check out a page using Visual Studio, then edit that page in Expression Web, then check back in with VS.
So the answer really is no. Relying on FrontPage's version isn't acceptable, even if it has VSS at the back end, because we all know what a big heap of poop that is.
-
blowdart wrote:

numedia wrote: 
blowdart wrote: Is it me, have I missed it, or is there no method of tying it into source control?
You can tie into source control via the basic FrontPage or SharePoint check in/out. Otherwise, I check out a page using Visual Studio, then edit that page in Expression Web, then check back in with VS.
So the answer really is no. Relying on FrontPage's version isn't acceptable, even if it has VSS at the back end, because we all know what a big heap of poop that is.
I'm just waiting for Orcas, Expression design surface, css toos and VS's source control, shame it's such a long wait!
Which makes think, if there is an Orcas Express Web Dev, doesn't that make Expression web slightly redundant? -
numedia wrote:Oh I'm glad you said it! It definitly has some great features like support for ASP.NET, but otherwise I miss FrontPage! FrontPage 2003 feels much more polished that Expression Web does. Like you mentioned, Expression Web does not always do what you tell it to do... or it does it in seemingly random ways. And it's very common to get lockups when working with pages either locally or off the server. If I could find a way to get FrontPage to work correctly on Vista I would use that in a heartbeat, but as it stands Vista breaks basic functions in FrontPage that makes it unusable.
With FrontPage, I would always turn to it when needing to design something for Visual Studio since it's design surface was way better than VS. But now with Expression Web, they are about the same to me. I have so many problems designing in Expression Web that I end up just doing the design in Visual Studio. Now that's sad!
agree 100% -
numedia wrote:

cescotto wrote:
Have you tried DreamWeaver? Its template system and CSS support is amazing. It also can automatically get database informations from the remote server and lets you create queries and insert/delete forms just with a few clicks.
Used to use Dreamweaver, but couldn't stand the UI. It took took long to get things done and at the time there was no support for the full ASP.NET lineup. Perhaps that's changed now.
agree 100% - lame ui -
Minh wrote:

Chadk wrote: Sadly we are seeing alot of half-baked products that Microsoft is trying to push out the door way too fast. Just look at XNA... Waay too fast.
Well, this is the new MS with the more frequent release cycles. And, um, we've all been asking for this.
No one asked for half-baked software to come out faster. If they are being agile, then I would expect a solid base with a reduced feature set. Not a feature rich, buggy, p.o.s.
Still VS, kicks a$$. I use dreamweaver in combination, but only to have a rich code editor for the visual aspects of html. I can't stand front page, and I have been looking forward to expressions web. I guess I have to wait till it gets more mature. -
ronin1855 wrote:

Minh wrote: 
Chadk wrote: Sadly we are seeing alot of half-baked products that Microsoft is trying to push out the door way too fast. Just look at XNA... Waay too fast.
Well, this is the new MS with the more frequent release cycles. And, um, we've all been asking for this.
No one asked for half-baked software to come out faster. If they are being agile, then I would expect a solid base with a reduced feature set. Not a feature rich, buggy, p.o.s.
Still VS, kicks a$$. I use dreamweaver in combination, but only to have a rich code editor for the visual aspects of html. I can't stand front page, and I have been looking forward to expressions web. I guess I have to wait till it gets more mature.
frequent releases does not mean the software can be half baked. i hope MS pumps up the quality further in all their products. This is not the MS we want.
-
Well, I think w/ the advent of the service packs, you can have all 3 points of the golden triangle: features, time, budget.
-
Minh wrote:Well, I think w/ the advent of the service packs, you can have all 3 points of the golden triangle: features, time, budget.
Nope that is exactly not the compromise anyone needs. when a day's work is lost because of something that will be released in SP1 its better not to have used it at all. nothing against u Minh
hope u understand
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.