How do you "autogenerate" a "using" namespace for a class you typed in Visual Studio? Read along... More...
March 13, 2008 08:47 by
Ryan
Just ran into one of Bill Evjen's blog post about interesting Visual Studio Plugins and from there came across Visual Studio Gallery - Products and Extensions for Visual Studio.
I don't actually mess with my Visual Studio installation (except for CoolCommands) since as we know it's critical for work but if you feel like giving things a test drive then the items there looks pretty interesting. There's just too many new things going on and needs to be learned lately but trying things out than simply reading about them always is a good way to learn.
March 10, 2008 03:47 by
RyanI've done this a couple of times but I still tend to forget at times so
I might as well post here for me and hopefully someone else's reference.
To create a Windows Service see this article by Ken Getz :
Windows Services: New Base Classes in .NET Make Writing a Windows Service Easy
There
are a number of ways to install a windows service, one of which is
using installutil.exe but this post will be using Setup Project which
for me is a little easier to implement:
More...
March 10, 2008 02:56 by
RyanThe collapse/expand all project and the open containing folder (plus
other features) would save time/effort so check out this addin from
Gaston Milano. I've tried this out myself for sometime already and
didn't get into any issue so go give it a try.
http://weblogs.asp.net/gmilano/archive/2005/11/10/430240.aspx
I was trying to test multiple connections to my local IIS server when I
got the http status/error code above. This is because there is a limit
to the number of concurrent connections with Keep-Alive Enabled setting
ON.
http://www.experts-exchange.com/Web/Web_Servers/IIS/Q_20286298.html
So I unchecked "HTTP Keep-Alive enabled" and the issue was resolved.
But
when I run/debug from Visual Studio (for an application configured to
run on IIS) i got an "Unable to start debugging on the web server. An
authentication error ocurred while communicating with the web
server...". IMHO, the error messages doesn't quite help in debugging
but it turns out that Visual Studio just needs the the keep-alive
setting ON to work for applications configured to run on IIS. Turned it
back on and worked fine.