Congradulation ! and big thank you !

It works like a charm : i just installed a new umbraco 4.8 with uBootstrap, it was very easy to do and it works straight forward.

Also, very nice use of best practices => I learned some cool stuff just by looking at your code and architecture

Could you please tell me why you are using http://imageresizing.net/ instead of ImageGen ?

Hello again,

I have finished studying all your code, it's very nice.

I have some feedback :

• For the news, instead of using the .net cache, why don't you use the build in "Cache By Page" on the macro "NewsFeed" and "NewsList" with a Cache Period of 8 hours ?
• For the sitemap, we are using the umbraco package http://our.umbraco.org/projects/website-utilities/cultiv-search-engine-sitemap (the Razor version). So no need to create some code for it. (we didn't test it with umbraco 4.8)
• For the robots.txt, we are using http://our.umbraco.org/projects/website-utilities/cultiv-dynamicrobots, so for multiple sites, you can use  : "sitemap: http://{HTTP_HOST}/sitemap.xml" (we didn't test it with umbraco 4.8).
• Nothing to do with your package, but we also always use the package 301 Url Tracker : http://our.umbraco.org/projects/developer-tools/301-url-tracker

I have a question also :

why do you do ?

 void ClearHeaders(object sender, EventArgs e)
        {
            HttpContext.Current.Response.Headers.Remove("Server");
            HttpContext.Current.Response.Headers.Remove("X-AspNet-Version");
            HttpContext.Current.Response.Headers.Remove("ETag");
            HttpContext.Current.Response.Headers.Remove("X-Powered-By");
        }

duplicate post sorry, see my answer below

Hello again,

wow, thank you for the fast, big answer.

I have seen how to switched from ImageGen to ImageResizer (I check your "Logic" code :)) thanks.

On big sites with lots of images we had performance issues with imageGen, so i'll definitely test ImageResizer on large sites, thanks.

About the cache per page, the umbraco macro cache is flushed each time a node (whatever node) is published (so even if the 8 hours are not reached), so I guess it should work without the .net cache.

"I could've done it with just standard razor markup but I prefer to use the standar .net SyndicationFeed class" => good point ! thanks

• How do you find the transition from ClientDependency to Combres? Did you find the /config/Combres.config file? Have you been able to edit it? Does it work as expected?

About the transition from ClientDependency to Combres, I didn't use the first version of UBootstarp, so sorry I don't have an opinion about it.We are using Squish It

Did you have the problem discribed there : http://our.umbraco.org/projects/backoffice-extensions/ucomponents/questionssuggestions/33021-Upgrading-to-Umbraco-48-breaks-support-for-uComponents

I didn't noticed the Combres.config, thanks

• What do you think about supporting both css and less files? I've basically done this beacuse there are some developers that are not so keen in using .less, or simply more familiar with just plain css

I think it's great. Unfortunately, i didn't have a chance to play with "less" a lot before but it's really nice to have both of course.  And I never tried to use  a page like "EditLessFile.aspx.cs" in Umbraco before, that opens some cool options to me :)

 Cheers

Fabrice

Actually, i think it makes sence to use the .net cache for the news instead of the macro caching, otherwise the cache would be flush even if you publish a "text node"..

In a project, we are even using AppFabric to cache stuff so the cache is not flush if the app pool is refreshed..(but of course it doesnt make sence for Ubootstrap)

Thanks for the feedback Fabrice :)

Regarding the HeadersModule https://github.com/jorgelusar/ubootstrap/blob/master/src/Logic/Modules/HeadersModule.cs, there are two different things I'm doing there.

1. Getting the Etag right is difficult, so following the Yslow recommendation I'm simply removing the Etag from the host header.
2. The server shows it’s version as well as the version of the ASP.NET framework in the headers returned to client requests, and this could be seen as a potential vulnerability. Therefore, there are being removed and the end request. I also usually remove the Umbraco version in the host header for the same reason by setting <removeUmbracoVersionHeader>true</removeUmbracoVersionHeader> in the config/umbracoSettings.config

Thanks,

J

is working on a reply...