Skip to main content

Setup and Visual Studio / VS Code Integration

Ideas and feedback on our setup process and Visual Studio and VS Code integration...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. C# modules in the Quantum SDK are throwing reference errors

    Hi, I'm going through the samples in the SDK and while everything is executing fine, the IDE is showing a number of reference errors for libraries/namespaces.
    For example:

    Error CS0234 The type or namespace name 'Simulation' does not exist in the namespace 'Microsoft.Quantum' (are you missing an assembly reference?) Measurement

    Error CS0246 The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?) Measurement

    I don't see any errors within the Q# modules.

    Any idea what's going on? I'm using Visual Studio 2017 Enterprise.

    Thanks,

    RIck

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support Q# debugging in vscode

    Following this documentation debugging is possible with plain VisualStudio but not with vscode. https://docs.microsoft.com/en-gb/quantum/quantum-techniques-testinganddebugging?view=qsharp-preview&tabs=tabid-vs2017#debugging

    I do believe that full support of vscode is mandatory for the success of the Q# community. Most of the developers will not be necessarily experienced C# developers and will probably work on *nix based machine.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Code formatting

    in VS code I expect if i do Cmd+K +F I can format the code file to my settings. However, this extension indicates that a formatter is not provided.

    If you open source this it would be easy to add btw

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. F# Hello World Example

    If you have your visual studio 2017 templates avaiable on git hub, I am happy to add a F# one for your SDK

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the offer! We haven’t put our project templates out on GitHub yet, I’m afraid.
    Because we compile Q# into C#, if you use F# for the classical driver code, it needs to be in a separate project from the Q# code. It works fine, though; we’ve done it here.

  5. Intellisense for Q#?

    Would be great to have same capabilities as in C# (type comments, prediction, refactoring). Right now I'm not getting any with VS 2017 (qs code file is treated as abstract text tokens basically), but everything compiles and works fine

    7 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Setup and Visual Studio / VS Code Integration

Feedback and Knowledge Base