Xuar
There are 24 entries for the tag
Xuar
You can download the Xuar last release (we remember you that this version is alpha) in the Xuar project at Codeplex. Etiquetas de Technorati: Xuar
Although in the last months there were not too much modifications in the Xuar sources and the Xuar Live pages are not working better, the project is not left. The cause was the annual vacations and the work in alternative projects less complex than Xuar than allows to learn the new ASP.NET 2.0 characteristics with a better yield in the learning that if they were made directly on Xuar. We hope that soon we can see many good updates in Xuar. Etiquetas de Technorati: Xuar
This new version of Xuar uses the new technology Atlas to work with the webparts. The webpart will can use the new Atlas controls, but it will be in next releases. Etiquetas de Technorati: Xuar
After 10 days of holidays, and many time used in change of hoster and in a new ASP.NET 2.0 application, we added: use of Atlas in many webparts. use the new version of Webpartcomponents (Nsquared2) We are working (another time) in: To refresh the sitemap when the language changes To make a webpart with CRUD of the information of the users To solve diverse problems of the GridView working with webparts. The problems are with Webpartcomponents (Nsquared2) when I add...
We are working in: to refresh the sitemap when the language changes To make a webpart with CRUD of the information of the users To solve diverse problems of the GridView working with webparts To use the new version of Webpartcomponents (Nsquared2) To document the diverse components that are integrated with Xuar. Etiquetas de Technorati: Xuar
We said that we are still working in ... Recreate the sitemap when the language changes. Create a webpart to display and update the user info. Work with Atlas. And we did ... Implant Atlas. It is possible to be seen in the administration page, how when selecting different pages to see them in detail, they do not recharge the complete page. We use the control Atlas UpdatePanel. The rest of things are for the next weeks. ...
You can see Xuar On Line at this page: http://xuar.herensoft.net. Etiquetas de Technorati: Xuar
The Visual Studio 2005 Web Application Project Model is a new web project option for Visual Studio 2005 that provides the same conceptual web project approach as VS 2003 (a project file based structure where all code in the project is compiled into a single assembly) but with all the new features of VS 2005 (refactoring, class diagrams, test development, generics, etc) and ASP.NET 2.0 (master pages, data controls, membership/login, role management, Web Parts, personalization, site navigation, themes, etc). Etiquetas de Technorati: Xuar
We are working in ... Organize better the sitemap. Recreate the sitemap when the language changes. Create a webpart to display and update the user info. Install sample Xuar portal in a fixed hoster. Etiquetas de Technorati: Xuar
In these weeks (practically a month) we have done: To work much in diverse subjects, without advancing too much. To update to the new version the "Visual Studio 2005 Web Application Project Model". To localizate a good part of the content of the portal. To add 2 more webparts: RSS and HtmlFeed. To put own content of Xuar in the example data. To upload an example of Xuar to the URL: http://cdn2-1.at.vwdhosting.net/ To...
We are working in ... A SQlSiteMapProvider. Create a .SQL file with the database scripts to create the Xuar database. Etiquetas de Technorati: Xuar
We said we will do: What we did not finish the last week: To prepare the sources so that they are possible to be downloaded. To document the source code. To create more information of the project and to arrange it within the own portal. and... That the connected users can change the language of the portal. And we did: Then... although we have worked a lot, we have not...
We said we will do: To organize the project with the Visual Studio 2005 Web Application Project Preview. To obtain a first outline of the documentation. To solve the bugs in the remote server. To begin to locate the application. And we did: The Workspace of Xuar in GotDotNet had a rare problem and also we have had to create other that already allows the Source Control (it works correctly integrated with VS2005). ...
We said we will do: To prepare the source so that it is possible to be downloaded. To document the source. To create more information of the project and to arrange it within the own portal. And we did: I continue having problems to upload the sources to GotDotNet. I cannot use none of the three systems possible to manage the sources (I would like to use the system integrated with VS2005), non-receipt solution to my requirements of...
We said we will do: To convert the Edit Weblog module of Content.NET 0.9 to a WebPart. To make dynamic the connection of the new Weblog WebPart with the Calendar one. To create a new Webpart: HTML/Text external. To localize the Weblog WebPart. We did: We did not convert the Edit Weblog module of Content.NET 0.9 to a WebPart. We made dynamic the connection of the new Weblog WebPart with the Calendar one. You need...
We said we will do: To finish the 4 existing skins and to add one more. To convert the Weblog module of Content.NET 0.9 to a webpart. To connect the new Weblog webpart with the Calendar one. We did: To work in the 4 existing skins but we didn't add any more. To convert the Weblog module of Content.NET 0.9 to a webpart. To connect the new Weblog webpart with the Calendar one. (It does...
We said that we will do: To debug the diverse errors that there are still. To improve a little the aspect of skins and to add one more. To integrate in the system to mount the pages by code to the pages that are. To create a control calendar as a true webpart. To advance in the organization of the portal entities: Portal, Page, Modules, Skins, ... And we did: We have...
We are working to create the Default page by code, adding the webparts by code reading the page contents from data. And we did: It is already the Default page mounted (the modules that compose it) totally by code. All the pages that are called from the menu, already are really the same Default page. They lack the pages that are called from other pages. They are loaded by code as much the true Webparts as the generic ones (controls ASCX placed in WebPartZones). ...
After the vacations of Christmas, and once solved certain problems, we have made a new update of the first outlines of the package. Now, after give it a personalizeable and more aesthetic aspect, we are going to try to put on it a content (the host is still provisional) that reflects the advances and new features in Xuar creation. A new update with a better skin Default. Etiquetas de Technorati: Xuar
There is a new version of Xuar at http://hiony33-1.at.vwdhosting.net/. The update responds to the graphical personalization: use of master pages, themes, style sheets, skins and Chromes for webparts. We have created a webpart that is a skin selector (including all the scheme of design: master pages, themes, skins, chrome) and that allows to choose between 4 different themes or skins: Default Granite Paper Sand. First one has a different scheme and the others play with 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...
"Web Parts provide you with an entire programming framework that rests on top of the ASP.NET 2.0 Framework. This new framework has powerful features, enabling you to build Web applications that can be customized by Web site users and administrators at runtime." We can use some parts of this framework to show the portal modules and to bring them many characteristics used by the module system... And also many new characteristics of webparts, as the portal personalization by the user. We are testing the use of webparts to eliminate the bigger part of the portal code managing...
The new version of our portal Content.NET (Xuar) will use the news characteristics of ASP.NET 2.0 for the personalization of the appaerance: 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...
Xuar is the codename for the next release of Content.NET portal working with .NET Framework 2.0, VS2005 y ASP.NET 2.0. We want to use in Xuar the new characteristics of ASP.NET 2.0: master pages, providers, new controls, etc. to make of Content.NET Portal the best application CMS multilanguage. The first step is compile the portal core code with ASP.NET 2.0. Etiquetas de Technorati: Xuar,Content.NET