October 2006 - Posts
Like last year I will attend Tech Ed Europe. This time in Barcelona, a wonderful city. I prefer it over Amsterdam. I will arrive on November 6th, mid of afternoon.
It will be the chance to meet some of you and especially Frédéric Colin, Grégory Renard, Aurelien Verla authors on Tech Head Brothers.
Who else is coming?
This new release includes all adaptations to the toolkit working with the new version of ASP.NET AJAX.
There is also three new controls: DropDown, MutuallyExclusiveCheckbox, and ValidatorCallout.
You can download it on this page and online demos are available here.
Microsoft just released the new version of ASP.NET AJAX as Beta, there are going out of the CTP cycles.
With ASP.NET AJAX, developers can quickly create pages with rich, responsive UI and more efficient client-server communication by simply adding a few server controls to their pages. This new Web development technology from Microsoft integrates cross-browser client script libraries with the ASP.NET 2.0 development framework. ASP.NET AJAX provides developers building client-based Web experiences with a familiar development process and programming model that they already know from using server-side ASP.NET development. Because ASP.NET AJAX is integrated with ASP.NET, developers have full access to the built-in ASP.NET 2.0 application services and the entire .NET Framework.
ASP.NET AJAX is not just for ASP.NET developers. Developers targeting other server frameworks can take advantage of the Microsoft AJAX Library and reap the productivity benefits it provides. The Microsoft AJAX Library is a standalone collection of the standards-based Javascript classes included in ASP.NET AJAX. It’s supported by most popular browsers and can be used to build client-centric Web applications that integrate with any backend data provider.
With its integrated, multi-browser support, uniform client programming model and powerful server controls, ASP.NET AJAX makes incorporating AJAX functionality into Web sites, big or small, simpler than ever before. To see how some companies have already done this, visit the ASP.NET AJAX showcase. To see what features are currently available in the Beta, refer to the details on the Feature Matrix page.
If you’re transitioning applications built with the earlier “Atlas” CTPs to the ASP.NET AJAX Beta, we’ve provided a Migration Guide to help you get going quickly. You’ll also want to know about new features in the Beta and changes from the earlier CTPs to the Beta. We’ve prepared a detailed whitepaper that describes these changes and how to migrate your applications successfully. Read the Changes between the ASP.NET AJAX (“Atlas”) CTP and the v1.0 Beta Release whitepaper which is also available as a Word document and a PDF document.
I hope that it is running well with Webparts now.
Tonight I had the following issue; right clicking on a Team Query in Team Explorer and choosing 'Open in Microsoft Excel' gave the following error:
interface not registered 0x80040155
The solution I found was to run: C:\Program Files\Microsoft Office\OFFICE11>EXCEL.EXE /regserver
Now I can again open my tasks in Excel.
What? How can you link those two!!!???
I am working on Tech Head Brothers Authoring tool and it means that I need to provide a setup to all the authors. I did it following a real long tutorial in two parts:
And finally I had a setup that works on my machine. But as you know if it works on yours it doesn't mean that it works on all. Hey developers, an application doesn't need to run just on your machine ;-)
What was the issue on author machines?
The interesting part of the exception was:
System.IO.FileNotFoundException: Impossible de charger le fichier ou l'assembly 'office, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' ou une de ses dépendances. Le fichier spécifié est introuvable.
Office Version 12??? What the hell is this I use Office 2003 and VSTO 2005!!!
So I tried to add a reference to version 11 of office without any success because the version 12 was in the GAC. After some research I found that Web Expression was the one that installed the version 12 of the office DLL, and was causing the issue. Quick uninstall to find that VSTO was not able to create new VSTO projects in Visual Studio, so I tried uninstall/reinstall of VSTO for the same result. Will check that later.
Conclusion: NEVER INSTALL BETA SOFTWARE OUTSIDE A VPC.
More Posts