Hello, I'd like to share some tips to make a proper D IDE with VS.
Basically you can setup visual-D with VS-2012 shell
integrated+isolated.
It works fine you can compile...All right but what if you want to
setup some extensions ? You'll be (most of the time)stopped by a
message saying that you can't install it for your VS
version.(because basically people who makes extension doesn't
know that the shell version exist or they don't care or
whatever...)

If the extension is made for VS 2012 (Pro) then you can use it
for your visual-D environment based on VS shell:

Step1:
=====
Download the extension from the MS website so that you'll have a
*.vsix file in your download folder (so not directly from the
IDE).

Step2:
=====
Open your *.vsix file with 7zip.
You'll see a file named *.vsixmanifest

Step3:
=====
Select this file and in the context menu , click "Edit".
Then you'll get an xml file in the text editor.

Step4:
=====
Then both cases are possible.

Case 1:
------
if there is a node named <VisualStudio Version="11.0">, with
something like that:

<VisualStudio Version="11.0">
<Edition>Ultimate</Edition>
<Edition>Premium</Edition>
<Edition>Pro</Edition>
</VisualStudio>

then add <Edition>IntegratedShell</Edition> at the right place...
Save the file and close it. Come back to 7zip, it'll propose you
to update the
archive. Accept. Then you can setup your extension.

Case 2:
------
There is no node named <VisualStudio Version="11.0"> but
another one:
   <Installation>
     <InstallationTarget Id="Microsoft.VisualStudio.Pro"
Version="11.0" />
   </Installation>
In this case replace ".Pro" with ".IntegratedShell". Save the
file and close it. Come back to 7zip, it'll propose you to update
the
archive. Accept. Then you can setup your extension.

Step 5:
======
Try to setup the extension it'll work.
Restart or launch VS. Enjoy !

Tested at least with:
- ColorThemeEditor.vsix
- GitSccProvider.vsix
- IndentGuide.vsix
- MultiEdit.vsix (click same identifiers an edit them at once)
- ProPowerTools.vsix (big pack)
- SelectionHighlight.vsix (double click identifier, Highlight all)
- VSTextMacros-1.1.vsix (keyboard macros)

Thanks for the interesting hint. Any extension that you would especially recommend?

I also have a hint for VS 2012 users of Visual D (not limited to the shell): the watch and auto windows don't work too well with the default debug engine of VS 2012. If you go to Tools->Options->Debugging->Edit and Continue and enable "native Edit and Continue", VS will switch to the "old" debug engine that works a lot better. It will also enable the visualizer macros for the debugger that come with Visual D. These allow two watch strings and arrays more conveniently.

Rainer

On 07.05.2013 18:05, D-Ratiseur wrote:
> Hello, I'd like to share some tips to make a proper D IDE with VS.
> Basically you can setup visual-D with VS-2012 shell
> integrated+isolated.
> It works fine you can compile...All right but what if you want to
> setup some extensions ? You'll be (most of the time)stopped by a
> message saying that you can't install it for your VS
> version.(because basically people who makes extension doesn't
> know that the shell version exist or they don't care or
> whatever...)
>
> If the extension is made for VS 2012 (Pro) then you can use it
> for your visual-D environment based on VS shell:
>
> Step1:
> =====
> Download the extension from the MS website so that you'll have a
> *.vsix file in your download folder (so not directly from the
> IDE).
>
> Step2:
> =====
> Open your *.vsix file with 7zip.
> You'll see a file named *.vsixmanifest
>
> Step3:
> =====
> Select this file and in the context menu , click "Edit".
> Then you'll get an xml file in the text editor.
>
> Step4:
> =====
> Then both cases are possible.
>
> Case 1:
> ------
> if there is a node named <VisualStudio Version="11.0">, with
> something like that:
>
> <VisualStudio Version="11.0">
> <Edition>Ultimate</Edition>
> <Edition>Premium</Edition>
> <Edition>Pro</Edition>
> </VisualStudio>
>
> then add <Edition>IntegratedShell</Edition> at the right place...
> Save the file and close it. Come back to 7zip, it'll propose you
> to update the
> archive. Accept. Then you can setup your extension.
>
> Case 2:
> ------
> There is no node named <VisualStudio Version="11.0"> but
> another one:
>     <Installation>
>       <InstallationTarget Id="Microsoft.VisualStudio.Pro"
> Version="11.0" />
>     </Installation>
> In this case replace ".Pro" with ".IntegratedShell". Save the
> file and close it. Come back to 7zip, it'll propose you to update
> the
> archive. Accept. Then you can setup your extension.
>
> Step 5:
> ======
> Try to setup the extension it'll work.
> Restart or launch VS. Enjoy !
>
> Tested at least with:
> - ColorThemeEditor.vsix
> - GitSccProvider.vsix
> - IndentGuide.vsix
> - MultiEdit.vsix (click same identifiers an edit them at once)
> - ProPowerTools.vsix (big pack)
> - SelectionHighlight.vsix (double click identifier, Highlight all)
> - VSTextMacros-1.1.vsix (keyboard macros)

On Thursday, 9 May 2013 at 19:06:58 UTC, Rainer Schuetze wrote:
>
> Thanks for the interesting hint. Any extension that you would especially recommend?
>

hi is there a free version of VS 2012 one can use ?

Nick

On 10.05.2013 09:28, Nick B wrote:
> On Thursday, 9 May 2013 at 19:06:58 UTC, Rainer Schuetze wrote:
>>
>> Thanks for the interesting hint. Any extension that you would
>> especially recommend?
>>
>
> hi is there a free version of VS 2012 one can use ?
>
> Nick

As the OP wrote, you can use Visual D with the free Visual Studio Shell (VS without any language): Install the isolated package

https://www.microsoft.com/en-us/download/details.aspx?id=30670

and put the integrated package on top of it:

http://www.microsoft.com/en-us/download/details.aspx?id=30663

After that you can install Visual D.

On Thursday, 9 May 2013 at 19:06:58 UTC, Rainer Schuetze wrote:
>
> Thanks for the interesting hint. Any extension that you would especially recommend?
>
> I also have a hint for VS 2012 users of Visual D (not limited to the shell): the watch and auto windows don't work too well with the default debug engine of VS 2012. If you go to Tools->Options->Debugging->Edit and Continue and enable "native Edit and Continue", VS will switch to the "old" debug engine that works a lot better. It will also enable the visualizer macros for the debugger that come with Visual D. These allow two watch strings and arrays more conveniently.
>
> Rainer

All of those listed previously. I haven't tested yet the Git extension because of no public project now. Otherwise:
- VSTextMacros.
- SelectionHighlight (but it seems to conflict with MultiEdit).
- IndentGuide.

Oh and as you're there, thx for VisualD !