Topics
01 Jan 2017, 15:25
 2460
 1
Replies

Dmitriy
05 Jan 2017, 13:01

RE:

Hi guys,

I see that size of the text cannot be controlled in Drawtext method.

When are you going to add this feature?

As for now - is it possible to change default size anywhere?

 

Thanks in advance,

Dmitriy

 

Spotware said:

Thank you for your idea. We will consider it. Additionally you can post it to vote.spotware.com.

 


@Dmitriy

Dmitriy
30 Dec 2016, 13:36

RE:

Hi guys,

I am trying to find a way how to compile CALGO file from Visual Studio but using VB.NET.

I have been working in VB.NET for quite some time and learning C# would be quite an effort. Compiling and building from C project in VS 2015 works like a charm but I really need a solution to compile CALGO file from VB.NET environment.

How is CAllgo file is compiled? From .dll compiled from C project or?

Thanks in advance,

Dmitriy

 

 

 

gainer said:

Since i answered a couple of topic i saw this is a matter that interest many of us, I opened this subject with all the instructions to FULLY integrate the cAlgo with the Visual Studio 2015 Community Edition

This is the complete procedure

  1. Above all, if you don't have it yet, download and install the powerful but TOTALLY FREE Visual Studio 2015 Community Edition

    https://www.visualstudio.com/en-us/products/visual-studio-community-vs.as

    Take a seat and a good coffee because the installation is really long!

  2. During the installation, you can choose the full version (with web development, C++, Visual Basic, Python and much much more...) or select only our loved C# environment for a lighter implementation

  3. Download the extension visual studio package https://visualstudiogallery.msdn.microsoft.com/e3279d0a-8002-4773-b8d3-bd70f57c27f7
  4. The vsix is simply a zipped file, unzip it in a folder as "VSExtension"

  5. Enter in the folder and you'll see the file "extension.vsixmanifest"

  6. Open the file "extension.vsixmanifest" with a normal text editor

  7. Add the references to the visual studio community edition between the eligible products
     

    <VisualStudio Version="11.0">
      <Edition>Community</Edition>
    </VisualStudio>
    <VisualStudio Version="12.0">
      <Edition>Community</Edition>
    </VisualStudio>
    <VisualStudio Version="13.0">
      <Edition>Community</Edition>
    </VisualStudio>
    <VisualStudio Version="14.0">
      <Edition>Community</Edition>
    </VisualStudio>
    <VisualStudio Version="15.0">
      <Edition>Community</Edition>
    </VisualStudio>

     

  8. This is the complete code, you can also copy and past it in the extensione.vsixmanifest in place of the current one

     

    <?xml version="1.0" encoding="utf-8"?>
    
    <Vsix Version="1.0.0" xmlns="http://schemas.microsoft.com/developer/vsx-schema/2010">
      <Identifier Id="2c72cc50-6c69-4b16-b1f4-ab470673f284">
        <Name>cBots and Custom Indicators</Name>
        <Author>Spotware</Author>
        <Version>1.4</Version>
        <License>EULA.txt</License>
        <Description xml:space="preserve">Building cBots and Custom Indicators in Visual Studio</Description>
        <Locale>1033</Locale>
        <InstalledByMsi>false</InstalledByMsi>
        <SupportedProducts>
          <VisualStudio Version="10.0">
            <Edition>Pro</Edition>
          </VisualStudio>
          <VisualStudio Version="11.0">
            <Edition>Pro</Edition>
          </VisualStudio>
          <VisualStudio Version="12.0">
            <Edition>Pro</Edition>
          </VisualStudio>
    	  <VisualStudio Version="11.0">
            <Edition>Community</Edition>
          </VisualStudio>
          <VisualStudio Version="12.0">
            <Edition>Community</Edition>
          </VisualStudio>
          <VisualStudio Version="13.0">
            <Edition>Community</Edition>
          </VisualStudio>
          <VisualStudio Version="14.0">
            <Edition>Community</Edition>
          </VisualStudio>
          <VisualStudio Version="15.0">
            <Edition>Community</Edition>
          </VisualStudio>
    	</SupportedProducts>
        <SupportedFrameworkRuntimeEdition MinVersion="4.0" MaxVersion="4.0" />
      </Identifier>
      <References>
        <Reference Id="Microsoft.VisualStudio.MPF" MinVersion="10.0">
          <Name>Visual Studio MPF</Name>
        </Reference>
      </References>
      <Content>
        <VsPackage>VSExtension.pkgdef</VsPackage>
      </Content>
    </Vsix>
    

     

  9. Now from within the directory, zip again all the files in a new "VSExtension.vsix" (be carefull to include all the files, but NOT the directory)

  10. Double click on the new vsix you just created within your directory... and it's done!

Wait for the installatione, then try it: within cAlgo select the "Edit in Visual Studio" option from the left drop down arrow menu near the name of one of your cBots/Indicators and after a while, it will appear within Visual Studio 2015 Community with the fully integration we want

That's all and have a good job!

 


@Dmitriy