[There's a reason that Yoda is the unofficial mascot of SBS.  Size indeed matters not.] People who understand .Net apply here - THE OFFICIAL BLOG OF THE SBS "DIVA"
Mon, Apr 23 2007 18:35 bradley

People who understand .Net apply here

People these days always say thing like .. "oh does it have the source code?" or "oh is it open source?"

Well...here's the thing folks... the ability to look at the underlying code only helps you if you know what the heck you are looking at.  For most small business owners, heck for most small business integraters, looking at the "source" code is like me reading KB821268, looking under the hood of the blog server and trying to figure out exactly where in the .NET 2.0 machine.config file that I'm supposed to enter some words and values to try to get Yoda to stop sucking CPU cycles.  Well.. at least I hope that is the trick because right now I know that I haven't a clue about what I'm doing.

Oh yeah, I can do a search of the Community server site and find stuff... like posts on forums and what not...and yup I've followed that one and it's not helping...

Application Pool setup screenshots - Community Server:
http://communityserver.org/forums/p/482755/560894.aspx

But when you aren't a coder, and you haven't a clue what you are doing, all this is is "data" not "valuable information" when you don't have a clue of what you are doing and the KB articles assume a basic level of knowledge that isn't in my noggin'. 

To me, this what the business decision maker in me makes the cut between stuff for the firm (the business) and stuff for ... well the blog.

S*U*P*P*O*R*T

The level and quality of support of a product are what make me stay with a product, leave a product, look forward to the next product.  And while, I'm sure all of us will agree support with Microsoft products can be dicey sometimes, if you get to a support person who knows their stuff, you relax knowing that your server is in good hands.  If you don't have that trust of the person "driving" your server, you are in for a bumpy ride.  Right now this server has a bumpy ride because it's primary support person (aka ME) hasn't a bloody clue (as Nick would say) and so far I don't think I'm helping and only hurting with my taking the bits and pieces along the way.

Because I'm not trained in this, and getting bits and pieces of stuff along the way, I'm not getting the right answer, I'm just getting data that I think might be the answer.  We see this in network configurations, don't we?  Someone who gets a bit of information from over there... and a tad from this blog over there...and you end up with network ....or in my case.... a blog server that isn't too healthy and well thought out.

<sigh>

Pardon me while I go find a real expert in this stuff because I really don't have a clue....

Contention, poor performance, and deadlocks when you make Web service requests from ASP.NET applications:
http://support.microsoft.com/kb/821268/en-us

<processModel maxWorkerThreads="100" maxIoThreads="100" minWorkerThreads="50">
<httpruntime minFreeThreads="176" minLocalRequestFreeThreads="152">
<connectionManagement>
              <add address="IPofserver" maxconnection="48"/>
</connectionManagement>

Filed under:

# Vlad Mazek - Vladville Blog &raquo; Blog Archive &raquo; Strange Monday &#038; Goings On

# re: People who understand .Net apply here

Tuesday, April 24, 2007 9:50 AM by Evan Anderson

Having access to source code is only marginally useful. Having access to source code licensed in a manner that allows you to hire any qualified party you choose (lowest bidder, fastest turnaround time, best references, etc) to work on that code is wonderful.

"Open source" has no clear cut definition. To me, "open source" means what I said above, and in that marketplace, competition is fostered between software service providers. (I could go on and on about how the software industry has deluded itself into thinking it's some kind manufacturing industry, instead of the service industry that it clearly is, but I won't go there in this comment... *smile*)

Anyone who thinks that "open source" is about end user Customers reading / servicing the source code is missing the point. Likewise to people who think that the point of "open source" is to get software for no cost.

Yes, enthusiast end users may be into reading the code, but the real value, to business, comes from being in control of your "own destiny", and having the freedom to make choices about when a program is no longer "supported" yourself-- not at the whim of the "owner" of the source code. The up-front expense of acquiring licenses for software, to a business, pales in comparison to the total cost of ownership (support services, training, process development, "soft" costs), and evaluating software ("open source" or not) on up-front cost is short-sighted.

# re: People who understand .Net apply here

Tuesday, April 24, 2007 11:40 AM by Tim Long

I think you've put your finger on the achillies' heel of Community Server - in fact, open source software in general. Until recently there was no documentation at all covering installation and administration. Now there is a wiki, but it still leaves a lot to be desired. It took me a good year and and least two major versions of using CS before I was really comfortable with the administration. Developers of this kind of product just assume that end users will have the same realm of understanding that they have. That just isn't the case. Even as someone familiar with .Net development, ASP.Net is a specialization within that and it was still hard for me to get to grips with it.

# Excuse the mess

Wednesday, April 25, 2007 4:15 AM by Nick Whittome - "The Naked MVP"

In an attempt to sort out the msmvps.com site, I spent last night cleaning out the databases (over 9gb