Published on June 26, 2008
in Tips.
Here are some other “minor” features (support for the new C# syntax and Linq being the major feature for me) that I really like in the new ReSharper 4.0:
- New capital letter completion in R# (i.e.: typing CCM in R# Type Navigaton instantly brings you ClientCoreModule). This type of completion still feels a bit weird but it just works for me.
- Solution-wide analysis (like background compilation in VB)
- Support for custom file headers (adding and updating all these copyrights)
- R# code annotations for the BCL (although I still haven’t tried to annotate my own classes). I can see Spec# type of functionality probably coming out of this in the future.
BTW, letter auto-completion works in Launchy as well. For example: typing MVS will bring Microsoft Visual Studio.
Over the weekend I’ve upgraded my development machine to Intel Core 2 Quad Q6700 (4 cores x 2.66GHz) from Core 2 Duo (2 cores x 2.4 Ghz that were usually running at 2.6-3.0 GHz).
Coupled with Windows Server 2008 64bit being used as a workstation, I can now have more Visual Studio instances and virtual machines running in parallel without affecting the performance. And the Resharper is lightning fast on any development solution.
That’s the point of any upgrade.
PS: it was really nice of Windows to start up without any problems (this could be a bug) after the processor change, automatically detect new processor, install the drivers and suggest to reboot.
Just finished playing with the Microsoft Project Server 2007 (or MSPS for short).
MSPS is server-side addition for the Microsoft Project that provides functionality for the centralized project storage, publications, global resource pool management etc. Additionally there is web access for it that provides lightweight readonly interface to the project data, allows to view assignments and schedule changes. And also, due to integration with the Share Point technology, there is the ability to manage project-related documents, risks, issues etc.
Continue reading ‘Checking out Microsoft Project Server 2007′
In this post I’m just kicking out one item from my “to do list“.
Being a developer means that you tend to stick to your keyboard instead of wasting time to reach for the mouse and do some movements. That’s why learning R# shortcuts could yield an immense productivity boost in your .NET projects. Same principle applies to the other areas outside your IDE as well.
Launchy (aka “Open Source Keystroke Launcher for Windows”) is just like your {Ctrl}+{N} Resharper shortcut for your Windows Operating System. And it is also extensible, skinnable and works. I’ve used HiddenMenu and PStart before, but this tool is way more efficient.
BTW, do you know, that you can type something like *Report in R# type search and it will work?
Here’s minor thing that just made the code feel a little better:
using (var inputStream = _inputFile.PostedFile.InputStream)
using (var stream = _fileStore.Create(tempInfo))
{
inputStream.PumpTo(stream, 128.Kb());
}
128.Kb() is more friendly to the eye than 1024*128
As you may already know, it is a common trend for some developers to use Windows Server 2008 for the development environment. I’ve done the same thing a couple of months ago (picking 64 bit version).
Here are some advantages of this:
- Performance is a bit better than in Vista (and it is more stable as any server has to be)
- It is said that 64 bit support here is better than in the previous OSes (64 bit support allows you to use more than 3GBs of RAM and utilize you Intel Core 2 processors more efficiently)
- Some trojans and viruses will have hard time running under 64 bit.
- It forces you to get familiar with the new technologies and concepts by Microsoft (I did skip Vista)
- It is free for 240 days
Update. Although, Windows Server and Windows Vista share the same codebase, there are yet diffs in the configuration (that’s not just about running services) that give some edge to Server 2008 in the overall performance. Here are some links:
Continue reading ‘Using Windows Server 2008 64 bit as a development workstation’
Published on June 21, 2008
in Tips.
If VS 2005 stops responding when opening ASPX (or other web related files), do not blame any add-in, try to uninstall/repair everything (including Layered Service Provider stack) or search for VS hotfixes/KB articles. Wasting hours on all that could be of little help.
Just make sure first, that your W3 publication service has not hung up.
This, increased friction and the need to do “Install VS2005 SP1″ routine, is the primary reason why I feel I little bit uneasy when there is need to switch back to 2005 for some projects.
Latest Comments