Contents tagged with VS.NET
-
Updating Azure Functions Tools
Azure Functions Tools is at the heart of providing local development for Azure Function. Whenever you use Visual Studio, Rider, VS Code, or anything else, you need it to be able to run your bits. For command line folks, the installation process is outlined in the tools repository. For Visual Studio (2022) and Rider, it is less evident as it depends on the tool. So, where am I heading with this? Right, the need to update the Azure Functions Tools.
-
Visual Studio 2012 Update 2 CTP – Browser
I have ran into an interesting message when opened a user group site in Visual Studio (not something that I usually do) and it made me wonder
-
Rename Visual Studio Window Title
Today have learned from RSS feed about Rename Visual Studio Window Title extension for VS2010. A great help when working with several branches of the same base code. Borrowing one of the screenshots from the official blog to show it.
-
PowerGUI
In my last post I have described the move from NAnt to PSake that is based on PowerShell. One missing piece for making the whole experience smooth was Visual Studio support for PowerShell syntax and some Intellisense. Gladly, I have run into PowerGUIVsx, that does just that: syntax highlighting, intellisense, and even debugging. Sweet!
-
Developing with Elevated Privileges – Gods’ Syndrome
Are you developing on Windows 7? Do you have your UAC turned off?
-
Mocking Extension Methods
Daniel Cazzulino had a very helpful post about how to mock extension methods. The only part I don’t like about this method is the fact you have to make internals visible to the test assembly using an assembly directive:
-
Right Tool for the Right Job - Part 2
In the previous post I talked about running test in Resharper vs. TestDriven.NET
-
Keeping Automated Builds DRY
This is not the first time I came back to automated builds and re-evaluate how they are done. This time, I wanted to capture several things at the same time:
-
SP1 and Scott Guthrie
Ok, so I was really upset and spilled a bit more than probably should have to. ScottGu has picked my desperate yell from the blog and suggested a help (2nd time I believe - 1st one occurred when .NET 2.0 SP1 has broken our production web sites, wow, he's good). Apparently there was an issue with SP1 Beta and R# 4.0. I already went through refresh on installs (including removal of addins and components). Plan vanilla .NET FW with Service Packs with no addins installed works fine (well, not crushing, working without R# is impossible).
-
SP1
As you probably know, the all new and shiny SP1 for both .NET framework and VS.NET 2008 are out. So I waited a bit, saw that other developers are accepting it and installed it. Great, worked smooth. Till I dared to restart. After that VS.NET 2008 designer "empowered by new abilities deployed with SP1" has showed own of it's hidden jams - complete crash of the IDE with no traces to what has just happened.