Skip to main content

Fast way of opening vs code from windows explorer

I like to find thing using Windows Explorer. I'm used to it. Before in tools like Visual Studio you could only double click the solution file and you where ready to go. Bot in Visual Studio Code (Code) you need to open though Code or cmd.

Before I used to find the project folder i Windows Explorer and then type "cmd" in the address field. Cmd would open and I typed "code .". But then I would have to you two steps, and I would have a hanging  Cmd window each time I open a project. Yes i'm lazy one could just close the open ones, but still adding one more step.

The solution for me was the fact that you can add arguments in the address filed in Windows Explorer. So when I typed ' cmd /c "code ." '  Code will open directly. Nice back to one step, and the best part Windows Explorer remebers the command.

Solution:
cmd /c "code ."
Labels:

Comments

Post a Comment

Popular posts from this blog

CSOM System Update that does not update minor version number

I was in a scenario where I had to do a add some data to a document list in a web job. My issue was that I could not find any system update method in the CSOM API. After searching it i found a blog post showing that one could just override the system fields, like Modified and Editor(Modified My). That seemed to work but that did not stop it form updating the version number of the document. This example will only work for minor unpublished version. I have not found a way to do this without a published version. There it will get a new minor version. The solution combines the use of adding Editor, and Modified with the use of the ValidateUpdateListItem metod. I found that one can set the item values on the item and just set one value in the form value list, then it will update all the fields. If one then set the "bNewDocumentUpdate" it will not update the version number if it is a minor version. So what i do is just get the values from the item before an update, then sets...
Post a Comment
Read more

The future of sandbox solution

Probably old news, but I was wondering what will replace SandBox solution. Because how else would we deploy stuff to SharePoint Online without WSP's, After some searching on the net I found this blog entry on SharePoint dev blog (link below). That states that the managed code part of SandBox solution is going to be removed, not the declarative parts like content types, lists, modules, etc, This will still be supported in what they call a no-code SandBox Solution (NCSS). I must say that it is nice to know that you can still use the ok part of the SandBox solutions, https://www.blogger.com/blogger.g?blogID=921264504943302831#overview/src=dashboard
Post a Comment
Read more