0 Comments

This was going to be from Word, but I ran into errors. Maybe it worked. Darn this looks professional. Winking smile

So, here we are after BlogEngine.NET, then adding multi-blog, moving the DNN which was a nightmare (Although DNN is a great product), and at last migrating to Orchard.

What did I learn.  I used to blog more!!!  Even when I mostly blogged about blogging.  I’m too busy to learn and add on to the likes of Orchard or DNN because ultimately, I used them to support others who could not see the benefits.  This new opportunity makes it easy to use, to enhance, to style, to Blog.  Hey, I even tried Open Live Writer and like what I see, but it seems like everything else (for example, CodePlex, WebMatrix, Windows Live Writer) “new” technology doesn’t last.  That’s OK.  I’m here to embrace it.  Blogging itself may have been replaced by Twitter, Facebook, LinkedIn, etc., but what’s next?

For someone who was early to the internet, and then spent a lifetime learning, there is no end in sight.  Open Live Writer and MiniBlog had a lot of open source help to get where they are, and seem to be well past “early” release, yet not quite long in the tooth yet.  What’s next?

(Yes, all of those links are intentional.  I hope I can provide a small link to the community. I will try harder in the future.)

0 Comments

I'm moving to DNN for various reasons, but mainly because as good as BlogEngine.NET is, it's a bit limiting.  I'd like to find a way to integrate it with DNN, but it would be better if there were a BlogEngine.NET DNN module, but I'll take what I've learned from this product and do the best I can at creating a new DNN Blog module that compares well with BlogEngine.NET.

I also want to get back to blogging.  It has been a long time coming and I have several Blogs to update, as well as Chats and Forums to support.

See y'all soon.

0 Comments

Current Multi-blog enabling LINQ to SQL BlogEngine.NET Provider. (Updated 3/12/10)

I have been asked for this code so that we can share the multi-blog solution that has been working for me for almost a year now.  This is the time to check it out and help make it work for yourself and others.  I’m going to continue to “dog food” this here.  Current version of BlogEngine.NET supported by this provider, as of this post, is 1.6.0.3.  Although I need to update my own site(s) from 1.6.0.1.

 

How will I update?

Mine is easy.  Drop in the new DLLs.

If I do a code “diff” and find the Web code to have changed recently (which I’m sure it did) I will copy those specific files to the Web folder.

 

How do you update from a cleanBlogEngine.NET 1.6.0.3code base?
  1. You should download the latest BE.NET code from codeplex and create a folder for the solution. 
  2. Extract the code from the zip into your solution folder. (…and follow the directions for setting up a stand-alone SQL Server Blog)
  3. Copy and unzip the BlogEngine.Linq2SQL.3-12-10.zip folder into the solution folder with the Core and Web projects.
  4. Add an existing Project to the solution, select the BlogEngine.Linq2Sql project.
  5. Verify the References (to project “BlogEngine.Core”)
  6. Add a reference to “BlogEngine.Linq2SQL” from the “BlogEngine.NET” Web site.
  7. Change Target Framework on BlogEngine.NET Web site to “.NET Framework 3.5
  8. Execute the SQL build script “Linq2SqlUpdate.sql” to add schema to support Multi-Blogs.
    • Make sure to run against the Database you created in Step 2.
  9. Assuming you are using the correct connection string, modify the Web.Config
    • blogProvider, membership, roleManager
    • See: Web.Config.xml

For those who like pictures to verify what you’re doing, here are a couple.  I’d rather have an installer but I’m not quite there yet.

Step 3:

Step3

Step 4:

Step4a Step4b Step4c

Step 5:

Step5

Step 6:

Step6 Step6b

Step 7:

Step7

Step 9:

1: <BlogEngine>
2: <blogProvider defaultProvider="Linq2SqlBlogProvider">
3: <providers>
4: <add name="Linq2SqlBlogProvider" type="BlogEngine.Linq2SQL.Linq2SqlBlogProvider, BlogEngine.Linq2SQL" connectionStringName="BlogEngine"/>
5: <add name="XmlBlogProvider" type="BlogEngine.Core.Providers.XmlBlogProvider, BlogEngine.Core"/>
6: <add name="DbBlogProvider" type="BlogEngine.Core.Providers.DbBlogProvider, BlogEngine.Core" connectionStringName="BlogEngine"/>
7: </providers>
8: </blogProvider>
9: </BlogEngine>
10:
11:
12: <membership defaultProvider="LinqMembershipProvider">
13: <providers>
14: <clear/>
15: <add name="LinqMembershipProvider" type="BlogEngine.Linq2SQL.LinqMembershipProvider, BlogEngine.Linq2SQL" passwordFormat="Hashed" connectionStringName="BlogEngine"/>
16: <add name="XmlMembershipProvider" type="BlogEngine.Core.Providers.XmlMembershipProvider, BlogEngine.Core" description="XML membership provider" passwordFormat="Hashed"/>
17: <add name="SqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="BlogEngine" applicationName="BlogEngine"/>
18: <add name="DbMembershipProvider" type="BlogEngine.Core.Providers.DbMembershipProvider, BlogEngine.Core" passwordFormat="Hashed" connectionStringName="BlogEngine"/>
19: </providers>
20: </membership>
21: <roleManager defaultProvider="LinqRoleProvider" enabled="true" cacheRolesInCookie="true" cookieName=".BLOGENGINEROLES">
22: <providers>
23: <clear/>
24: <add name="LinqRoleProvider" type="BlogEngine.Linq2SQL.LinqRoleProvider, BlogEngine.Linq2SQL" connectionStringName="BlogEngine"/>
25: <add name="XmlRoleProvider" type="BlogEngine.Core.Providers.XmlRoleProvider, BlogEngine.Core" description="XML role provider"/>
26: <add name="SqlRoleProvider" type="System.Web.Security.SqlRoleProvider" connectionStringName="BlogEngine" applicationName="BlogEngine"/>
27: <add name="DbRoleProvider" type="BlogEngine.Core.Providers.DbRoleProvider, BlogEngine.Core" connectionStringName="BlogEngine"/>
28: </providers>
29: </roleManager>

0 Comments

But why is it now different from BlogEngine.NET 1.5.1.46?

I downloaded it yesterday and Diffed to find out what I need to change to keep up…and it was the “version number.”

So, I guess keeping up with several code changes over the past few months and making sure my version of the Multi-blog capable SqlBlogProvider was in tune paid off, only to realize I’m still one of the very few to implement such a “clean” version of multiblog BlogEngine.NET.  I’ve been working on an Entity Framework provider since this could replace or certainly enhance the capabilities of BlogEngine, but it may really be just another stepping stone to work out a new architecture to support BlogEngine-Like capabilities for .NET 4.0 and IIS 7 using MVC, Entity Framework and perhaps WCF for integration and remote administration capabilities.

At least I’m learning a lot about Open Source capabilities and limitations. Does anyone want to legitimately tackle a Next Gen BlogEngine with me?  Of course, I would not want to steal the branding created here unless there is a parallel effort to create a distinctly separate single Blog, Multi-user system such as BlogEngine.NET and a more scalable, database centric, multi-blog, real-time administration console application.

Design first, Agile methodology, Eat-your-own-dog-food approach with lots of prototyping.

Or I could just use BeerHouse or DotNetNuke, I guess.  Need to go get some additional experience.

 

See Y’all l8r,

Dave (BizTron)

0 Comments

A few widget improvements

As commented on by BenAmada:

 

I think it would be more ideal to create a new widget that does what you're looking for -- rather than modify the TextBox widget.  Others have asked to be able to output Google AdSense code or other pieces of Raw HTML into widgets.  It never works very well with the TextBox widget.

A new, very simple widget could be created that has a multi-line textbox in it (not tinyMce), and raw HTML would be pasted into the textbox.  I know this widget would be perfect for the AdSense and other Ad people, and sounds like it might fit what you're looking for too.

LiteralWidgetClipHere is a quick Literal Widget created on suggestion since it helps me with one of my own issues.

Thanks “BenAmanda”

 

Widget:

Please try this and let me know if you have made any improvements.  It’s simple and not tested extensively and came right out of the TextBox widget, but without tinyMce and simple required mods.