Using BlogEngine.NET with aspdotnetstorefront - Newbie

Topics: Themes
Apr 6, 2012 at 10:46 PM

I've been tasked with finding a blogging engine that will work with aspdotnetstorefront. The company has a sophisticated template that wraps around their content and they would want the blog to run within that container. I'm not familiar with .NET, so I don't know if this is possible/easy.

Anyone out there have some help for the n00b?

 

Thanks

Apr 9, 2012 at 7:15 PM

The skinning of the BlogEngine.net is pretty easy so you should be able to have it match up with the AspDotNetstorefront skin no problem.  We did the same integration with www.emeraldbiosystems.com a couple years back, shared the stylesheets and JS files across the applications. You will lose some of the store functionality once you get to the blog (minicart etc). For ours we removed the whole account login/logout piece but you could probably frame that in to allow direct access to your users' accounts.  For all intents an purposes you could probably frame in a bunch of the AspDotNetStorefront functionality, we found that to be a bit messy and just let the blog be the blog while having all of the store navigation in place.

Apr 9, 2012 at 7:26 PM

Okay, this might be a dumb question…

I looked at the Emerald Bio site, and it seems that the blog has a similar (but slightly different) menu. Does this mean that the blog is using a copy of the main navigation instead of pulling in the navigation, same as the rest of the site?

In other words: you’re duplicating the skin for the blog, not dropping the blog into the main site’s architecture/skin/whatever. Is that right? And that’s what you mean when you said that we could use a frame to pull in the main site’s navigation?

Yeah, I can see how that would get messy. We’d really like to avoid having the navigation in two places if possible. If we’re going to allow comments, we’d prefer to have a single sign-in for the whole site, rather than one for the blog and one for the commerce side.

Thanks for the response!

Apr 10, 2012 at 7:11 AM

AlienRex,

Not a dumb question at all :)

To have the website have a global navigation, where all pages in the entire website uses only 1 navigation and not a copy of one you need to have

a nested master page.

http://msdn.microsoft.com/en-us/library/bb547109.aspx

 

In the parent master page just put the contents that would be in all of your pages main site and BE blog pages.  Like your navigation and footer.

Then for your 1st child master page have the content of your main site in one child.

Then for 2nd child page master page have the BE content there.

In total you will have 3 master pages.

Global.site.master 

Main.site.master 

BE.site.master   

That solves your navigation part.

 

For the login issue have a single login.   Meaning you have to merge your membership provider with each other so that you have only one.

Then your users only have to login in once to access both the blog and your main site.

 

Here a useful link to help you out with Single login:

http://blogengine.codeplex.com/discussions/267003

 

You can also do a search for "Single Login"

 

Hopefully this gets you where you want to go.

 

Have a good day,

 

Brian Davis

 

 

 

 

Apr 10, 2012 at 4:50 PM

Excellent - very helpful. Thanks a lot Brian, your explanation makes perfect sense.

Rich(AR)

From: kbdavis07 [email removed]
Sent: Monday, April 09, 2012 11:11 PM
To: Rich Barringer
Subject: Re: Using BlogEngine.NET with aspdotnetstorefront - Newbie [blogengine:351487]

From: kbdavis07

AlienRex,

Not a dumb question at all :)

To have the website have a global navigation, where all pages in the entire website uses only 1 navigation and not a copy of one you need to have

a nested master page.

http://msdn.microsoft.com/en-us/library/bb547109.aspx

In the parent master page just put the contents that would be in all of your pages main site and BE blog pages. Like your navigation and footer.

Then for your 1st child master page have the content of your main site in one child.

Then for 2nd child page master page have the BE content there.

In total you will have 3 master pages.

Global.site.master

Main.site.master

BE.site.master

That solves your navigation part.

For the login issue have a single login. Meaning you have to merge your membership provider with each other so that you have only one.

Then your users only have to login in once to access both the blog and your main site.

Here a useful link to help you out with Single login:

http://blogengine.codeplex.com/discussions/267003

You can also do a search for "Single Login"

Hopefully this gets you where you want to go.

Have a good day,

Brian Davis