Filed under: Windows
January 12, 2009 • 4:30 pm 0
Microsoft temporarily removes Windows 7 Beta download limit – Engadget
July 25, 2007 • 12:15 am 0
Windows Server 2008 beta 3
Yesterday I installed the new windows server 2008 beta OS. I was really surprised by its speed of installation and operating. After looking around I managed to turn on the nice looking graphics and sound 
So now it’s like I’m running vista, but with all the nice features of a server OS.
The thing I really like is the fact that you can say what needs to be installed like the server roles and features. Server roles already existed in Windows Server 2003 but they have been extended as well as optimized using new wizards and so on. The new thing is features. If you want to enable sound this is now a feature. I think there are about 73 features you can enable or disable.
To be honest this system looks like vista, feels like vista (actually is vista) but runs faster than my previous vista environment and you get the extended possibilities a server has got to offer. In my opinion I would advice this for developers wanting to develop for vista instead of doing it on vista. It’s like developing on windows server 2003 for windows xp.
Filed under: Windows
July 2, 2007 • 3:05 am 0
How to ignore a blogging career ?
That’s simple buy a house that needs to be finished in the meantime switch jobs and on top of that move out of your current appartement. 
I’ve not been writing as much as would like, but I can’t seem to find the time. Lately I’ve been watching more closely to LINQ, Nhibernate, EDM, Windows Server 2008 and Visual Studio .net Codename ”Orcas”… I know that’s a lot but I can’t keep up and I would like to explore as much as humanly possible under current conditions.
Anyways my findings in short are:
LINQ: nice
NHibernate: same as LINQ = nice + advantage current support .net 2.0 and older versions.
EDM: yeah well… nice as well
Windows Server 2008: mmm still beta, should say enough.
VS.Net Orcas: surprisingly “stable”.
Filed under: .net, .net 2.0, .net 3.0, .net 3.5, Visual Studio .Net "Orcas", Windows
February 15, 2007 • 11:14 pm 1
How to: Print from ASP.Net on a network server
Yesterday we had a small problem with a project of ours. We have a reporting system that server side will process the report and if configured it will print this on a printer somewhere in the network.
When we first tried this every time we printed to a network attached printer we got an error saying that we did not have access to this printer. This behavior is actually normal if you think about it. The server side code runs through an ASP.NET Web Service which in our case runs under it’s native aspnet account. Since this is a local account it does not have access to the network printer.
A solution could be impersonation or just simply make sure the web service runs as a dedicated domain account that has access. This however was not an option for us so we had to look for something else.
The solution I came up with was creating a local printer, but instead of letting it print to a local port like LPT1 I created a new standard TCP/IP port. This allows you to enter an IP and port for the networked printer. The advantage is that this printer is a local printer which requires no authentication at all, so asp.net can use it to print without knowing that it is actually being sent to a network printer.
Filed under: .net, Asp.net, Asp.net 2.0, Windows
