December 2005 - Posts
PageMethods for VS 2005 has been updated with various fixes and improvements. Note that an
FAQ is now available.
Please update your version. Please uninstall the previous version first.
Details about the updates since the official release:
- version 1.5.1.0 (bug fixes and improvements)
- It is now possible to activate and deactivate the PageMethods add-in directly from projects' properties, without having to proceed through the Web.config file.
- PageMethod's strong-named assembly can now be called in shared web hosting environments (details).
- version 1.5.0.2 (bug fixes)
- PageMethods was not handling correctly projects under IIS.
- version 1.5.0.1 (bug fixes)
- Take into account the additional namespace added in Web.config when using the ASP.NET Configuration tool, as described here.
- Added some code to keep Intellisense (code completion) more in sync with your modifications.
- Added some code to avoid problems with some kinds of projects (like SQL Server Reporting Services projects).
The new
Web Project Option for Visual Studio 2005 is now available as an alpha version. Its new name is the "Visual Studio 2005 Web Application Project Model". You can get all the details on
Scott Guthrie's weblog and on
the dedicated web site.
As reported by Aaron Robson, you should use the
AllowPartiallyTrustedCallers attribute if you want to allow strong-named assemblies to be called by partially trusted code. This is needed for shared web hosting environments.
Shared hosting environments usually run under a Medium Trust security setting. In Aspnet 2.0 this has changed somewhat, and one of the effects is that any strong named assembly must have the [assembly:AllowPartiallyTrustedCallers] attribute. This is a problem if you're using third party code and they haven't updated it. One workaround is to set <trust level="full" /> in the web.config file (within system.web element) - although I suspect hosts shouldn't allow this to work.
I will include this in
PageMethod's next release. In the meantime, you can use the workaround with the configuration file.
Quick reminder: you can win a
SmartInspect Professional license if you subscribe to SharpToolbox' newsletter. As a subscriber to this newsletter you automatically participate to our raffle.
We already have two winners. The next one will be drawn soon. Don't miss your chance and subscribe now at
http://SharpToolbox.com
A new -old- web project model option is coming for VS 2005 The ASP.NET team takes a look back at VS 2003's model for web projects and adds an option to Visual Studio 2005 to use the same kind of model. This has been requested by several users when the new model (no project file, multiple assemblies, App_Code folder, etc.) was introduced.
It looks like this new option can be the best of both worlds, as it still lets you take advantage of the new VS 2005 WYSIWYG designer changes (no more html reformatting, master page/theme designer support, etc), as well as all the
improvements made in the html source editor, and it lets you use VS 2005's built-in web server and MSBuild.
See also the new
Visual Studio 2005 Web Deployment Projects Congratulations to the ASP.NET team for its newly gained agility!
Update: this new model is available as a preview.
My new article has been published: Using LINQ, DLINQ and XLINQ for application development.
It is currently available only in French, but translation is pending. In the meantime, you can use your favorite fish for translation.
Of course, I'll let you know when the English version is available.
Update: This article is now available in English as well.
Mon nouvel article intitulé Exemples de mise en oeuvre de LINQ, DLINQ et XLINQ a été publié sur DotNetGuru.
Introduction : Cet article met l'accent sur l'utilisation de LINQ, DLINQ et XLINQ pour le développement d'applications. Il s'agit uniquement d'un exemple de mise en oeuvre, et non d'une architecture de référence ou d'une utilisation optimale de ces technologies. Le but n'est pas d'expliquer comment fonctionne Linq mais plutôt d'explorer les multiples facettes de Linq au travers de bonnes pratiques.
Ajax? Why ajax? This guy at
TrimPath has different applications: they run entirely in the browser. He calls them
SPADE, single page applications that include a built-in development environment.
Just take a look at
Next Action for example, a
Getting Things Done todo-list tracking tool.
Over at
TrimPath.com, you'll also find open-source components to build this type of applications. These crazy things include:
- JavaScript Templates, which lets you have template-based programming (like PHP/ASP/JSP) while running in a web browser.
- TrimQuery, a 100% JavaScript query engine that features an embeddable SQL syntax.
More Posts