Last post Oct 24, 2006 10:11 AM by mbowles
Jan 30, 2006 10:44 AM|mh8759|LINK
Just installed this add-on and finally!! everything works as I'm used to. Now I can include/exclude with a simple touch of a button, use subprojects, sub sites and everything else that worked in VS.NET 2003. I don't understand why you had gone into such
major changes, when things don't get easier but get worse. And I consider myself advanced web developer.
VS 2005 has numerous great features but managing complex/advanced web projects was not it's strong side, thanks to this update things changed.
So thank you for making the things the way they should be in the first place.
Although it comes a bit late (just spent a week changing projects back and forth to make my 2003 projects work) it is still great!
Jan 30, 2006 11:27 PM|ScottGu|LINK
Cool -- I'm glad you like it!
We will be coming out with an update for it in about a week that adds more features. In particular, it will support auto-generation of control field declarations (a big missing feature today), as well as support for migrating a VS 2003 code behind page
or a VS 2005 web site page to the web application project approach.
Hope this helps,
Jan 31, 2006 03:56 AM|mh8759|LINK
I've just encountered an issue. I have two websites in my solution, then try to drag and drop user control from solution explorer from one site to another. VS drops only link in the designer window. What's with that? If a drag and drop user control that
is member of one website project on pages in the same projects everything works well.
Jan 31, 2006 11:30 AM|ScottGu|LINK
Web Application Projects don't yet support the ability to drag/drop user controls from the solution explorer into the design surface and have it automatically set the <%@ Register %> directive. This is on the list of features still to implement.
Instead, what you'll want/need to-do is to manually add the register directive to the top of your .aspx page, and then declare the user control in source view. Once you declare it, you can then flip to the design surface and manipulate the control using
the designer (just like web site projects). The only thing that needs to be done manually is declaring it.
Feb 06, 2006 07:27 PM|cgsturm|LINK
I started using the new Web Application projects add-on too. I am very glad to have this coming from VS 2003.
I too notice that the user controls are no longer drag/drop capable. Also, style sheet drag/drop appears to not work also. Looking forward to the next update.
Feb 06, 2006 08:47 PM|ScottGu|LINK
Yep -- this is still on the list of things to implement. In the meantime, you'll need to add stylesheet references and user-control declarations in the .aspx file using source view.
BTW -- here is a blog post I just did about the update we are doing this week for the Web Application Project:
Feb 07, 2006 03:26 PM|vgl|LINK
As far as I understand it is still Beta version of this feature. Does anyone know when the real version will be available?
Feb 07, 2006 05:53 PM|ScottGu|LINK
My blog post above provides more of a roadmap update. But our goal is to have the feature-set finalized the end of next month.
Feb 08, 2006 12:00 PM|jnapier|LINK
Will Microsoft support both models moving forward? I have moved my 2003 project to the web project model that comes with vs.net 2005. It took me about a day and I still have some bugs to work out. I have heard lots of complaints about the new web site
model. Since I have went through most of the torture of converting already, would it make any sense for me to move to the web application project?
It seems like the new web site model may be better for content rich sites that ned to be updated on the fly and the web application project would be better for a code rich site. Is this what the major reasoning would be for using one project over the other?
Feb 08, 2006 01:22 PM|ScottGu|LINK
Yep -- both models will be fully supported going forward. If you are using the VS 2005 Web Site Model today and happy with it, then you should definitely use it going forward.
We are going to be coming out with whitepapers that describe the differences and pros/cons of each option for different scenarios over the next few months (each option can be used for pretty much all scenarios -- but some are more optimal than others).
Feb 08, 2006 06:08 PM|Jesse Towner|LINK
Feb 08, 2006 11:34 PM|ScottGu|LINK
It will be pretty easy to migrate from the web-site project model to the web application. My blog post (http://weblogs.asp.net/scottgu/archive/2006/02/05/437439.aspx) shows a little
how to-do this -- basically you just add your pages into the project and right click and choose the upgrade option to migrate them to use the new project system option. I'll post more detailed tutorials on how to-do this over the next week or two.
For right now, you might choose to just start with a web-site project -- with your business classes cleanly separated into class library projects. We are planning on having the VS Web Application Project feature complete in late March -- so if you want
to migrate then (or even before then), that will also be an option for you to consider doing.
Feb 09, 2006 10:34 AM|mh8759|LINK
Feb 09, 2006 11:26 AM|ScottGu|LINK
The memory corruption error and debugging problem you are seeing is a known issue that is documented with the first preview -- it basically occurs if you keep the exception assistant enabled and manipulate documents while debugging is occuring. If you turn
off the exception assistant checkbox in tools->options you shouldn't see this issue at all (several people who have had this instability have changed this setting and have all reported that things worked fine after that). The new refresh build that we are
shipping this week turns off the exception assistant for you by default -- so people won't run into this error.
I have not heard of any issues with .designer.cs files being deleted. Are you sure this is the case (the first preview today doesn't ever touch them -- so it is unlikely that the IDE is doing this)?
If you want to send me email (firstname.lastname@example.org) I'd be happy to send you the latest build (which we will be publishing shortly on the web). It has more features, automatically updates the .designer.cs file
with control declarations, and also has a number of bug fixes.
Feb 09, 2006 12:19 PM|jminond|LINK
On the site, you mention "With the next refresh of the VS Web Application Project download, we will add context-menu support in the solution explorer for automatically converting an existing code-behind page into two separate files "
.. when do you predict this feature will be added, and available for download?
- Jonathan Minond
Feb 09, 2006 12:39 PM|ScottGu|LINK
Our plan is to have it available for download either today or tomorrow. If you send me email (email@example.com) I can send you the build a little early.
Oct 24, 2006 09:28 AM|mbowles|LINK
Oct 24, 2006 10:11 AM|mbowles|LINK