Welcome to Rainbow Portal Community Sign in | Join | Help

ASP.NET 2.0, Multiple projects in the solution, No Esperantus and more!

ASP.NET 2.0, Multiple projects in the solution, No Esperantus and more!

  • Web
    • holds your modules and pages, etc...
    • web.config, rainbow.config ( why can't we joing them ? )
  • AppCode
    • Contains all the zen code, and raiinbow folders code
  • Rainbow.Framework.Web.UI.Webcontrols
    • contains rainbow localized web contros, using global resources folder
    • doing things like object str = HttpContext.GetGlobalResourceObject("Resource", key);
  • Rainbow.Settings

Sample of replacments for Esperantus using native .net resources

   1:  <rbfwebui:localize id="moduleLocationLabel" 
   2:       runat="server" 
   3:       text="<%$ Resources:Rainbow, AM_MODULELOCATION %>">
   4:  </rbfwebui:localize>

What we have attained is a fully compliant asp.net 2.0 solution. Bringing us much closer to anything we want to do with
providers, themes, master pages etc.... we also have a seperat space for core developers, web control developers,
resource people are in the web space with global resources

Solution Image

In the image to your left you can see that there is one solution with a web project that includes App_GlobalResources, App_Code, App_Themes, and App_Data folders.

There is also a note about the removed rainbow core code folder

Also at the bottom you see a project called Rainbow.AppCoder (this will be converted to Rainbow.Framwork over time.

There is anohter project of interest Rainbow.Framework.Web.UI.WebControls which contains asp.net native localized controls used throughout the project in place of esperantus controls.

 

also here is the whole solution so far...

As you can see there is a web project, an AppCode ( Which will migrate to Rainbow.Framework ), and a few other projects.

On Disc the structure is like this

  • /Projects/
    • /AppCode/
    • /Framework.Web.UI.WebControls/
    • /Settings/
    • /Provider/
    • /Provider.Implementation/
    • /Configuration.Provider/
  • /WebSites/
    • /Rainbow/
   

 

 

The main things here are going to be ( Once the solution is more stable, and the url problems are gone ):

  • Pushing the use of asp.net theme and master to replace classic engines
  • Replacing Solopart Menu with asp.net 2.0 native menus, which means we need ansqlSiteMapProvider
  • Constant Issue solving and bug squashing
  • Cleaning up setups, possibly creating a new and improved installer.
  • Getting a couple solid people to work on Rainbow.Framework.Web.UI
  • Getting people to overtake individual modules, improving, updating and cleaning them. DataGrid's replaced with GridView...etc...
  • Getting people to work on Rainbow.Framework.DataStore and Rainbow.Framework.DAL Api's
  • Getting Rainbow.Framework.Permissions done
  • Starting Rainbow.Framework.Content
  • Starting Rainbow.Framework.Content.Categories
  • Checking and Improving the implenetation of General.GetString() - Since it's called a lot, it needs to be fast

'

The following image is a sample shot of rainbow running with my currnet enviroment, sure it's filled with bugs... but there is no esperantus, and it is a full asp.net 2.0 solution :-)

Published domenica 19 febbraio 2006 17.50 by Jonathan

Comments

# re: ASP.NET 2.0, Multiple projects in the solution, No Esperantus and more!

lunedì 20 febbraio 2006 0.17 by ramseur
Hmm interesting. I saw this in the beginning as a method. The appCode should be renamed to Core since that is the core code of rainbow. I wanted it to be in the app_code folder so it would be precompiled and ready for rainbow. However, Putting it in its own project is nice too as it completly seperates it out and still provides it in an assembly. Please try to make your code as a release level with lowest bugs as possible. Submit an official change log and blog [ of course] about your release. Also, talk with me before you make something release ready. Doing a great job as always and keep up with the good work.

# re: ASP.NET 2.0, Multiple projects in the solution, No Esperantus and more!

lunedì 20 febbraio 2006 3.14 by Jonathan
I need to figure out the virtual path problem fiirst, before i can continue ironing out any other issues.
i figured out rewrite.net is rewriting fine, but the asp.net runtime is throwing an exceptino on a virtual path check for the url that is the unrewritten version..... even though it has already been rewritten ( see the erro rmessage in the forum i am discussing this )

# re: web.config, rainbow.config ( why can't we joing them ? )

lunedì 20 febbraio 2006 15.17 by Yannick Smits
I don't understand either why some of the appsettings are in web.config and some are in rainbow.config.

Maybe it is time to start using the Microsoft.Practices.EnterpriseLibrary.Configuration
This will allow for richter configuration options like categorisation and storage of more complex data

# re: ASP.NET 2.0, Multiple projects in the solution, No Esperantus and more!

lunedì 20 febbraio 2006 15.33 by Jonathan
We already have most of thie config stuff managed by Rainbow.Settings.Config ( i think ) so we should be able to do anything we want... the new asp.net 2.0 web.config already allowes for hierarchial stuff i tihnk....
We should look into how to better manage our existing config, using System.Configuration.Configuraition mangager...
In my code base, most config settings are upgraded to used COnfigurationMangaer, i also moved the connectionstring to the <connectionstrings> web section in web.config.
</connectionstrings>

# re: ASP.NET 2.0, Multiple projects in the solution, No Esperantus and more!

martedì 21 febbraio 2006 8.58 by wforney
It's nice to see that my work wasn't just thrown out by everyone. The last commit I did before the svn changed and I lost commit access was up to the point where esperantus was my main problem. Now that you've worked that out I may have some time to jump in and continue a bit later this week.

# re: ASP.NET 2.0, Multiple projects in the solution, No Esperantus and more!

martedì 21 febbraio 2006 19.05 by Jonathan
Bill.... I am looking foward to your help and guidance

# re: ASP.NET 2.0, Multiple projects in the solution, No Esperantus and more!

mercoledì 22 febbraio 2006 0.52 by ramseur
Bill, All your code was also loaded to the new SVN which you have rights to. I also agree with jon that we should use the standard out of the Box ASP.NET 2.0 ways to control configuration. This allows for .NEt proggers to quickly get moving with our system since they already know it. Second, its good to have a Rainbow.config or at least a user.config to allow for development and user specific changes like connection strings. This way you can get all the recent changes to the general web.config and add your user specific.
Anonymous comments are disabled