Improvements to non-VisualGDB components

Sysprogs forums Forums VisualGDB Improvements to non-VisualGDB components

This topic contains 3 replies, has 2 voices, and was last updated by  MystikReasons 1 month ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #27431

    MystikReasons
    Participant

    Please support UNC paths for building projects.

    Our whole company is structured like this.

    VisualGDB build log:

    “\\swionserv2.company.ch\PROFILES$\name\Client\Desktop\project”
    CMD.EXE wurde mit dem oben angegebenen Pfad als aktuellem Verzeichnis gestartet.
    UNC-Pfade werden nicht unterstĀtzt.
    Stattdessen wird das Windows-Verzeichnis als aktuelles Verzeichnis gesetzt.

    • This topic was modified 1 year, 9 months ago by  support.
    #27443

    support
    Keymaster

    Hi,

    This is a limitation of Windows, not something specific to VisualGDB. Please contact Microsoft if you would like to suggest an improvement to the logic in cmd.exe.

    #27454

    MystikReasons
    Participant

    I’m currently testing out your redesigned Quick Debug feature and I noticed that I can’t browse for debugged files in my own NAS cloud because it’s not showing up.

    Could you change this?

    Edit: myCloud from Swisscom (their cloud solution) is also not showing up

    • This reply was modified 1 year, 9 months ago by  MystikReasons.
    • This reply was modified 1 year, 9 months ago by  support.
    Attachments:
    You must be logged in to view attached files.
    #31728

    MystikReasons
    Participant

    When creating a project via “File->New->VisualGDB Project” and you try to browse for a location you can not find network attached storages like OneDrive, Dropbox etc.
    Would it be possible to change this completely so it uses the Windows File Explorer?

    Attachments:
    You must be logged in to view attached files.
Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.