microsoft / microsoft/vscode-powerquery-sdk
Power Query SDK for Visual Studio Code Offline Install
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 92
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Preflight Checklist
- I have installed the latest version of Power Query SDK.
- I have checked existing resources, including the common issues and the release notes.
- I have searched for similar issues.
Power Query SDK
0.2.3
Regression From
No response
Platform
Windows
Architecture
x64
OS Version
Windows Server 2016
VSCode version
1.82.2
PQSdkTool Path
C:\Users<username>.vscode\extensions\powerquery.vscode-powerquery-sdk-0.2.3-win32-x64
Bug Description
How can I do an offline Install of the Power Query SDK für VSC?
Our ProxyServer and Firewall do not allow access to Nuget. Downloading and Installing the VSIX File triggers a call to download the Nuget file. Downloading the file and providing it doesn't work. Copying the complete Install from a working client (not behind the proxy) doesn't work.
Whenever starting VSC or trying to work with the SDK this error comes: "Failed to update PowerQuery.SdkTools package due to socket hang up".
What is needed for an offline Install to work?
Steps to Reproduce
Have a Proxy that blocks traffic to Nuget
Install VSIX file for Power Query / M Language
Install VSIX file for Power Query SDK
Copy the .vscode\extensions\powerquery.vscode-powerquery-sdk-0.2.3-win32-x64 from a working installation
Start VSC -> Error
Open a PBI Custom Connector Project and try to evaluate. - > error
Actual Experience
Power Query SDK does not work allthough it seems all necessary files are there
Expected Experience
Power Query SDK works.
Additional Context
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reproducing the blocked-NuGet setup with the Power Query SDK VSIX and the copied extension directory, then trace the package update behavior. Done means the SDK starts and evaluates a Power BI Custom Connector without requiring NuGet access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100