Visual Studio 2008 and ComponentArt Web.UI

Posted Mon Jul 30, 2007 @ 2:30 PM


Now that Visual Studio 2008 Beta 2 has shipped, it's a good time to talk about the next version of ASP.NET and Visual Studio. More specifically, I am happy to share some good news on how Microsoft's next major platform release will affect ComponentArt's customers.
Scott Guthrie has a great post on ASP.NET AJAX in .NET 3.5 and Visual Studio 2008. I encourage you to read the entire post, but here are some key points you should take away from it:

"ASP.NET AJAX 1.0 shipped as a separate download that you could install on top of ASP.NET 2.0.  Starting with the .NET Framework 3.5 release, all of these features are built-in with ASP.NET, which means you no longer have to download and install a separate ASP.NET AJAX setup when building or deploying applications. When you create a new ASP.NET application or web-site in VS 2008 that targets the .NET 3.5 framework, VS will automatically add the appropriate AJAX registrations in your web.config file and the core ASP.NET AJAX server controls will show up in your toolbox."
"The V3.5 of System.Web.Extensions.dll is a fully compatible super-set of the 1.0 implementation (which means you don't need to change any code in order to use it)."  

As expected, ASP.NET AJAX has become a native part of ASP.NET and Visual Studio. We are extremely excited about this because it puts our customers in a unique position when it comes to exploiting the new features as well as gaining forward compatibility of applications based on ComponentArt Web.UI.

If you examine the ASP.NET component space today, you will notice that other leading vendors are currently in the early stages of developing component sets based on the client-side component model introduced with ASP.NET AJAX. These products are entirely new, and don't provide backwards compatibility with the current component offerings by those vendors.
In contrast, ComponentArt's customers will be able to enjoy seamless upgrading to Visual Studio 2008 and ASP.NET 3.5. All of your code based on the public APIs of ComponentArt Web.UI v2006.2 or later will be fully functional and in sync with the overall architecture and philosophy of Microsoft's new framework.
I think that great things are on the horizon with Visual Studio 2008. We anticipate that its adoption will be fast due to: multi-targeting features, new JavaScript IntelliSense and debugging, new web designer, as well as major improvements of the IDE performance.


Posted to I Build, Therefore I Am by miljan

Posted on Mon Jul 30, 2007 @ 2:30 PM

Filed under: , , ,


Posted on Mon Jul 30, 2007 @ 2:30 PM
I need componentAtr for VS.NET 2005.
Posted on Mon Jul 30, 2007 @ 2:30 PM
When is ComponentArt releasing a Silverlight 1.1 version of your UI controls?
Posted on Mon Jul 30, 2007 @ 2:30 PM


If you are using VS.NET 2005 you can download Web.UI for ASP.NET 2.0 or Web.UI for ASP.NET AJAX. Differences between various Web.UI framework builds are listed here.

Posted on Mon Jul 30, 2007 @ 2:30 PM
G, ComponentArt's strategic direction is to offer best of breed tools for web development. Without any doubt, Silverlight will play an important role in that space. We are currently working on identifying key areas where we could add value to the Silverlight platform. It is definitely too early to talk about release dates. However, you can rest assured that ComponentArt will be among the first component vendors to come out with solid, feature-rich Silverlight components that address the needs of real-life applications.
Posted on Mon Jul 30, 2007 @ 2:30 PM
I'm using VS 2008 exclusively on a Vista machine right now. Am I correct in that the ComponentArt WebUI controls will work with beta 2? I'm currently writing software which more than likely won't need a production date until it (VS 2008) is released in Feb but I just don't want to move back to 2005 unless I have to. The answere will decide if I purchase the controls right away or wait.
Posted on Mon Jul 30, 2007 @ 2:30 PM
Visual Studio 2008 Beta 2 is supported with the current production build of Web.UI. Please note that a web.config setting outlined in this knowledge base article needs to be applied so that the proper version of ASP.NET AJAX assemblies is referenced. Obviously, Visual Studio 2008 is still in beta, so we are looking for your feedback regarding any problems you run into while using our products with it.
Posted on Mon Jul 30, 2007 @ 2:30 PM
So, is it true that I'll have to upgrade by Web.UI 2006.2 version to Web.UI 2007.1 in order to use Web.UI with Visual Studio 2008 Beta 2?
Posted on Mon Jul 30, 2007 @ 2:30 PM
You should be able to apply the same web.config setting with our Web.UI 2006.2 for ASP.NET AJAX release to get things working with VS2008.
Posted on Mon Jul 30, 2007 @ 2:30 PM
Hi. When I debug apps that use CA components in VS.NET 2008 there is a lot of "anonymous code" generation in the debugger due to th amount of Javascript generated. Are CA aware of the time it takes for VS to generate all the separate chunks of code and make them available with the VS gui? Is this a recognized issue? Cheers, Ben
Posted on Mon Jul 30, 2007 @ 2:30 PM
unlucky for me. The page with ComponentArt treeview and grid control in ajax updatepanel cannot post back and raise button click event. The same thing happens on all my machines so that I ensure that's not environment problem. My version is 2007.1.1617.3. Please can anyone help me out of this issue? Appreciate! My mailbox is
Posted on Mon Jul 30, 2007 @ 2:30 PM
We are currently testing our products with the Release Candidate build of VS 2008. Ben, could you please elaborate on the behaviour you are seeing? Are you seeing this when trying to compile the Web.UI source code or your own project which contains a Web.UI reference? Eunge, we haven't been able to reproduce this problem. Could you please open a support request for this issue so that one of our engineers can work with you on reproducing it. Thank you very much for your help!
Posted on Mon Jul 30, 2007 @ 2:30 PM
It is great that there are plans to include silverlight as a platform for new controls. With SharePoint extending Asp.NET 2.0 and the next SharePoint SP1 release supporting the Ajax framework do you have plans to wrap any controls as WebParts? Some compainies are offering HTML Editors and other such controls as WebParts.
Posted on Mon Jul 30, 2007 @ 2:30 PM
Any hints on how to upgrade to componetArt 2008?
Anonymous comments are not allowed. Click here to log in or create an account.