A hotfix is now available for issues most commonly described as " Controls are not being recognized in the code-behind " and " Editing existing .aspx regenerates .aspx.designer.(cs), but most of the controls are now missing ”. This hotfix can be downloaded from: http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=27117 The update addresses the following Connect bugs: http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=532641 : Cannot embed standard asp.net controls in Ajax Control Toolkit TabContainer http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=533071 : Controls in CreateUserWizard WizardStep not visible as before http://connect.microsoft...(read more)
I’ll use a walkthrough example to show how to package a web application with speech API COM component using Visual Studio 2010. I wrote and tested the sample in Win7 x86 with IIS7.5, and packaged and manually installed to win2k3 x86 IIS6 (which only had 3.5 framework installed). 1. Create a C# 3.5 web application 2. Add COM reference to “Microsoft Speech Object Library” 3. In Default.aspx, add the following between <div> < asp : ScriptManager ID ="ScriptManager1" runat ="server"> </ asp : ScriptManager > < asp : UpdatePanel ID ="UpdatePanel1" runat ="server"> < ContentTemplate > < asp : TextBox ID ="TextBox1" runat ="server" Width ="274px">...(read more)
If we want to package and deploy COM component for a web application only, we can simply reference them and change their “Copy Local” property to “True”. For example, we can do the following to package a MVC project from VS2010. Create a MVC project In its references, change the following three assemblies “Copy Local” property value to True. System.Web.Mvc System.Web.Routing System.Web.Abstractions You can multi-select them and set the value together. Right click the project node and select “Build Deployment Package” Examine the package, you will see the above assemblies' corresponding dll files are included in the package’s bin directory. Deploy the above package to a 4.0 site, no matter if the corresponding MVC runtime is...(read more)
We have seen some customers report the issue that certain controls are not getting generated correctly in the designer file in Visual Studio 2010 RC for the ASP.Net Web Application Projects. We are currently working on a fix for this issue for the final RTM release. Workaround: You can work-around this issue by declaring the missing controls in the code behind file for the ASPX page. Example: When you add a Button control with ID as “Button1” to the aspx page normally you should see the following code be generated in the designer file for this control. VB: Protected WithEvents Button1 As Global.System.Web.UI.WebControls.Button C#: protected global::System.Web.UI.WebControls.Button Button1; If this code is not being generated in the designer...(read more)
Discount ASP.Net has updated their Hosting Sandbox for Visual Studio 2010 RC and ASP.NET 4.0 RC. http://www.discountasp.net/press/2010_02_16_free-asp.net-4.0-RC-hosting.aspx To learn more about the new Web Deployment features in Visual Studio 2010 check out this Step by Step Walkthrough on Web 1-Click Publish with VS 2010 To provide feedback on the RC please visit the Visual Studio Connect site . You can also contact the Web Tooling team directly by sending mail to vsweb@microsoft.com Bradley Bartz | Visual Web Developer Read More......(read more)
It’s finally here. Visual Studio 2010 and .Net 4.0 release candidate is available for everyone to download now. To download the public RC of Visual Studio 2010 go the RC landing page : Since the beta we’ve been focused on performance improvements, reducing memory requirements, increasing stability and fixing customer reported bugs. Here are just a few of the tweets flying around about the RC: @CanadianJames #vs2010 is fast like ambulances flying through a school zone at 120 mph being chased by ninjas. and the ninjas are on fire! @ddotterer Trying out VS2010 RC: Snappier UI, much faster intellisense, significant build time reduction, etc. Overall: AWESOME JOB! #vs2010 #vs2010RC @alazlasse Testing #VS2010 RC performance: loading solution...(read more)
Web project package and deployment targets files are written with extensibility in mind. User can easily extend a property to include more functionalities in their package by using msbuild targets and properties. If we check the Microsoft.Web.Publishing.targets file under “%Program Files%\MSBuild\Microsoft\VisualStudio\v10.0\Web\”, we can see the following, which means if file $(WebPublishPipelineProjectName).wpp.targets exists in the project directory, we’ll import it automatically when build package or publish. <!-- *************************************************************** --> <!-- To allow the Team build to have custom setting for the Web Application project without change the project file --> <!-- by default...(read more)
As you probably heard the Visual Studio 2010 RC is currently available for MSDN subscribers! You can download it from here http://msdn.microsoft.com/en-us/vstudio/dd582936.aspx . General public release is slated for Wed. The Web Development Tools Team has setup a DL that we would like you to use to send us direct feedback on anything web development related for this RC. The DL is: vsweb@microsoft.com Once you have had a chance to use the product please send us feedback on your overall experience with our product. The more details you can provide the better. Also, feel free to shoot us a mail if: You encounter a bug or issue. You have general feedback, suggestions or ideas on our web tools product. If you do encounter a bug please send us a clear...(read more)
When we released ASP.NET MVC 2 Beta back in November, I addressed the issue of support for Visual Studio 2010 Beta 2. Unfortunately, because Visual Studio 2010 Beta 2 and ASP.NET MVC 2 Beta share components which are currently not in sync, running ASP.NET MVC 2 Beta on VS10 Beta 2 is not supported. The release candidate for ASP.NET MVC 2 does not change the situation, but I wasn’t as clear as I could have been about what the situation is exactly. In this post, I hope to clear up the confusion (and hopefully not add any more new confusion) and explain what is and isn’t supported and why that’s the case. Part of the confusion may lie in the fact that ASP.NET MVC 2 consists of two components, the runtime and what we call “Tooling”. The runtime...(read more)
March 5, 2010