I note that you said .Net rather than any specific .Net language. I switch back and forth between Java and VB.Net, C#.Net and a smattering of C++.Net.
The main thing to bear in mind is that most languages share common roots and are to some degree similiar, therefore the first thing to do is to identify the differences. Keep them in mind and you'll be off to a good start in being able to port your existing knowledge to the new environment. The next thing to do is to check that your existing knowledge isn't overidden by some language feature you haven't come across previously eg. closures, special builtin classes/functions etc.
I also try to make sure that the IDE I'm using has:
- Common/configurable shortcuts.
- refactoring tools (either builtin or third party).
- Appropriate plugins for the toolset I'm using.
This serves mainly to reduce the time I spend "fighting" the IDE because I use shortcuts a lot, and I prefer not to leave the IDE to run things like Maven for example.
I would recommend books on the spefic APIs you'll be using, and make sure you have a good internet connection as Google is your friend :-)
There is always a few things that bug me about most languages (none of them are perfect) but none are killers. The little things include that VB declarations are opposite most other languages I commonally use nowadays, though having said that 15 years ago when I was using PL-1/PL-X a lot I would have been annoyed about Java/C* being opposite of my usual style.
I jump back and forth, and generally I try to use the most appropriate tool(s) for the job. The only disappointment I would have is if I used the wrong tool.