VS2005
There are 5 entries for the tag
VS2005
Thanks to use of "Visual Studio 2005 Web Application Project Preview" that allows to develop in way project the applications Web in VS2005 (that was what VS2003 did), we have made with a little effort a new version of our Content.NET portal that works with VS2005 and ASP.NET 2.0. The application does not incorporate any of the new features of ASP.NET 2.0 and VS2005 but it works and it can be compiled and be maintained with the new version of Visual Studio. The application follows with the same scheme that previously. The part of the portal core...
First I said: "The version 0.9.3 of Content.NET (the version in course at the moment) is developed with VS2003, ASP.NET 1.1 and NET Framework 1.1 (I believe) and it does not work with VS2005. We are developing a new version 1.0 of Content.NET (codename Xuar) taking advantage of all the ASP.NET 2.0 new characteristics, but it is in a very initial phase still. This version would be multilanguage naturally and would be based on Webparts. We have not considered to make a new version of Content.NET (the...
I am trying copy the actual app I am testing webparts with it, and I get this error: The 'System.Web.UI.WebControls.WebParts.SqlPersonalizationProvider' requires a database schema compatible with schema version '1'. However, the current database schema is not compatible with this version. You may need to either install a compatible schema with aspnet_regsql.exe (available in the framework installation directory), or upgrade the provider to a newer version. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in...
The new version of our portal Content.NET will use the news characteristics of ASP.NET 2.0 for the personalization of the appearance: the master pages, the themes and skins. Master Pages - The Master Pages feature provides the ability to define common structure and interface elements for your site, such as a page header, footer, or navigation bar, in a common location called a "master page", to be shared by many pages in your site. This improves the maintainability of your site and avoids unnecessary duplication of code for shared site structure or behavior. Themes and Skins -...
The new characteristics of VS2005 in skinning and themes had stopped all the works about the skinning in the Content.NET Portal, and others utilities as SkinConverter. Etiquetas de Technorati: Content.NET,VS2005