BKdotNET - Bill Knaus's Dev Blog

Blog Re-birth

BillKnaus — Wed, 07 Jan 2009 18:06:00 GMT

My blog has gotten... stale. Since my last post, I did a lot of good stuff at JPMorgan Chase programming wise... then moved on to Stanley Associates up in Dumfries for a year which showed promise at first, and then... not-so-much... and now I have my four mile commute back at a young defense contractor called ACGS, headquartered here in Fredericksburg. There are a lot of refreshing new challenges here... challenges I look forward to blogging about from a technical perspective. Most of the challenges center around working with GIS, creating/modifying GIS-driven apps, and working with video in a new and innovative way. My hope is that this isn't the last post you'll see from me on my geek blog for the next two years, and that this particular blog will start to really take off.

More soon.

Separate your documentation to maintain system autonomy

BillKnaus — Fri, 08 Sep 2006 21:04:05 GMT

Want to really know when everything went horribly wrong and you ended up tightly coupling something that was supposed to be modular or service oriented? Take a look at your documentation. More and more as I have been digging through our team's archives...(read more)

Communication is essential

BillKnaus — Wed, 30 Aug 2006 20:28:12 GMT

We are human beings. What makes us the intelligent creatures of the earth is our ability to not just communicate, but to communicate complex thoughts and ideas. It comes naturally to us to want to communicate and we learn to communicate at a very young...(read more)

Performance Monitoring ASP.NET apps - the art of the insane

BillKnaus — Tue, 22 Aug 2006 03:57:47 GMT

So Microsoft professes that all these fabulous counters in .NET that are available to the Performance Monitor tool provide a good level of insight... well bah! bah! I say. Consider a multi-tier environment with multiple approaches to remoting (.NET Remoting...(read more)

The FBI's Virtual Case File Failure

BillKnaus — Fri, 18 Aug 2006 15:15:36 GMT

Visiting the WashingtonPost.com today, I came across an article titled "The FBI's Upgrade That Wasn't". Working in Washington a couple years ago, and working in government at the time (not the FBI), I had certainly heard about the "Virtual Case File"...(read more)

Unlocking the Master Page mystery within CommunityServer

BillKnaus — Wed, 16 Aug 2006 06:25:46 GMT

I'm spending some time learning how CommunityServer implements master pages. Since they want to be backwards compatible with ASP.NET 1.1, they haven't adopted the ASP.NET 2.0 Master Pages. Instead, they've taken on a piece of community work from "MetaBuilders...(read more)

Windows Live Writer (beta) - A cool bloggin' tool

BillKnaus — Tue, 15 Aug 2006 14:33:00 GMT

One of the reasons why I find it difficult to spend the time to write a blog entry is the eventual "timeout" while I'm typing the thing up. I've had it happen before... entering the blog on the web form and spend 45 minutes writing something...(read more)

Day 4 configuring Microsoft's Customer Care Framework 2005

BillKnaus — Tue, 20 Jun 2006 23:49:00 GMT

My Customer Care Framework pilot setup experience continues... today's problems - the trials and tribulations of authorization and authentication with Internet Information Server 6... ...(read more)

Day 3 configuring Microsoft's Customer Care Framework

BillKnaus — Mon, 19 Jun 2006 18:33:00 GMT

Its Day 3 of my experience installing Microsoft's Customer Care Framework 2005 demo or pilot installation, and it is a lengthy task to take on from scratch......(read more)

Some useful Virtual Server setup and optimization tips

BillKnaus — Thu, 15 Jun 2006 21:26:00 GMT

I saw a WebCast today from TechEd in Boston given by Martin Granell. At the end of the web cast we received the URL to his blog to eventually get code from the session. Visiting Martin's blog uncovered more than just some cool info on Grandmothers and...(read more)

Microsoft does it again - ObjectDataSource - useful to a point - or is it?

BillKnaus — Mon, 20 Feb 2006 15:16:00 GMT

Has Microsoft stiffed experienced developers with the ObjectDataSource server control in ASP.NET 2.0? Or is the ObjectDataSource server control simply the "starter kit" - only without the source code?...(read more)

Gotchas with the Copy Database wizard in SQL 2005

BillKnaus — Fri, 27 Jan 2006 15:19:00 GMT

Yesterday I needed to copy a database from my local machine to one of our development servers... both the server and my local pc are running SQL Server 2005 Dev.

My first thought was to simply detach my database from my local, copy to the server, and then reattach on the server. As I right-clicked on the database, the last menu item caught my eye... "Copy Database..." I decided to see what this would do for me and "click" I began what started out to be a pretty cool journey...

The Copy Database wizard allows you to do the copy by the "detatch and attach" method (which I was willing to do by hand) or using the SQL Management Object method, which I wanted to avoid... (I wasn't in the mood).

So I go through the wizard just fine - some of the things I had to do to actually make it work....

These were both relatively "virgin" installs of SQL Server 05 Dev. So the first obstacle I ran into was Microsoft's new security initiative: Install with minimal risk exposure. In other words - I had to turn on Named Pipes and TCP/IP - on both servers.
The account that the SQL Agent service was running under on my destination server had to be running under an account that had access to a file share to the database file on the source server. Now- this isn't just the proxy account you can configure in SQL Server... this is the actual account the service runs as.

Now - at this point - everything transferred over beautifully - it even created the server login for my database... at least I had thought.

So the next thing I encountered were reports that no one was able to log in to the database at its new location. During the copy process, it might create the login, it might maintain the integrity of your database... but it doesn't link the server login to the database user. In fact - it made it quite impossible because now my database user is configured "WITHOUT LOGIN" and I can't change it. I unwire some of the dependencies that would allow me to drop the user - drop it - and recreate it for my login.

But my problems don't end there - people still are not able to use the account - final resort - I reset the password. voila.

Now - for this last part - is that all I had to do was change the password? Did I have to go through dropping the account? I don't know. But doing all of this worked. If you have a different experience - I'd be interested in hearing about it.

DotNetNuke ClientAPI and Microsoft's Atlas

BillKnaus — Fri, 27 Jan 2006 06:13:00 GMT

Jon Henning, the lead for the DNN Core Team ClientAPI team and creator of the SOLPARTMENU featured in DNN, provided some thoughts on the future of the DotNetNuke ClientAPI and Microsoft's Atlas in his blog. Having seen a recent video from MSDN on Atlas, due out sometime this year, there's a lot of potential for creating a richer user experience on top of DNN as this year unfolds.

Here are his thoughts.

Here is the video/demo on Atlas on MSDN.

And finally - the Atlas web site.

DotNetNuke's IUpgradeable interface for module controllers...

BillKnaus — Fri, 27 Jan 2006 05:45:00 GMT

I was going through the ASP.NET Forums for DotNetNuke and came across this post from "Sponge_Bob".

Is there anyway that I could run my own custom code on installation of my own PA's. I have a Module the need to be able to check and see if a certain Dll file is installed on the server before installing. Also I need the install to be able to check the version of the Dll file on the server an make certain the it is of the required version. Finally if the Dll not of the required version I want to point the person installing the PA to the place where to get the latest version of the install.

I have the option here to use Code (Preferred) or Sql to accomplish this task as I can make it so the required Dll I need to check for has its version entered into the database as it will be originally installed as a skin object.

It would be really sweet if Dnn could check the version of a Dll file before overwriting it with a dll file from a PA to make certain the it is not installing a Dll File of a lesser version. I am more that willing to write the code to accomplish this if the core team is willing to implement it.

So - I took a few minutes to help "Sponge_Bob" out. Here's my response...

I have to answer a question from Sponge_Bob. Dig yer username.

DotNetNuke provides an interface called IUpgradeable. The interface is implemented on your controller class for you module, similar to the way IPortable and ISearchable are implemented. There's very little written about this interface, however. The interface contract contains one method definition -

Function UpgradeModule(ByVal Version As String) As String

So digging a little deeper...

The the lastest version of the Private Assembly Installer (V3) will check to see if your BusinessController class supports the IUpgradeable interface. If it does support it, it will iterate through an ArrayList of versions and call your UpgradeModule implementation for each version.

So - similar to the way DNN does version control - you can handle each incremental upgrade... a nice litte switch / case statement on the version string sent in to your method.

Now if a needed DLL is not there - you could always throw an error... OR - use your string return to add an error to the module install... (that would be the kindler, gentler approach). Use HTML within the string to color the text red so it stands out. Well - you should always return a string at least letting the user know that each upgrade was successful. Any string you return will be added to the module install / parsing results.

Seeing that this is done during install of your module or module upgrade - I wouldn't recommend putting any code in here to check for latest version or anything like that. However, what I would recommend is creating a separate edit control for "Check for New Version" which can do that. Unless it is mission critical to push latest versions (i.e. OS Security Patches, Virus Software) I personally prefer choosing an option like that.

Considerations for Creating a Custom DotNetNuke Install

BillKnaus — Fri, 27 Jan 2006 03:17:00 GMT

I've just finished an article on how to customize the DotNetNuke installation package. I spent a few hours today digging around the DNN framework looking at how DNN does installs, how portal and host templates work, and how to specify which modules need to be installed... as well as how to not install some of the basic dnn modules. The more I dig around inside the framework, the more impressed I become with DNN (which says a lot since I've been impressed with DNN for quite some time). A lot of times when looking through other people's code, specifically some of the open source stuff out there, you get to a point and say - "ah - they're going to regret that they did that". I've been saying a lot of the opposite - "yeah - that makes sense" or "jeez, thats how I would have done it."

In this case, I was setting up a shared DNN development environment and realized that I hadn't "sanitized" my DNN 4 install yet... I ended up on a journey that has me dreaming about host templates, a common module set for all of our install points, and... and... our own portal that shows up after install with our own skin. Nice.

Take a read. It looks pretty lengthy - but i try to make it an easy read. If anything - especially for those developers visiting from work - you can get an idea of the capabilities this framework provides... and the power beneath your fingertips.

>> Article <<