-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question]: NuGet missing packages in local dev environment #1249
Comments
We would have expected the same, would be great if this works :) |
Hi @freddydk, I was wondering if you could provide an update on this issue. We’re looking into NuGet as a possible alternative to |
GitHubPackages should work. |
Usually our users do not have access to the private repository (ISV products) of other organisations. We would get provided with a PAT from the external organisation. New Question might be now: How to access the private nuget or GitHubPackages feed of an other organisation that will not provide access (justifiably) to their private repository and will only provide access via a PAT to reduce the permissions to a minimum (reading packages). We are currently in the same situation, we would have to give many users access to our repository as external collaborators, which also generates costs |
@freddydk this is also why only providing symbols is not sufficient. But as for a solution to your problem. We use the https://github.com/BusinessCentralApps/GenerateBcNuGet Repo to generate a Nuget feed thats contains the runtimes which then can be shared by inviting our partners to that organisation. This is currently not a perfect solution and be mainly use it to distribute runtimes for onprem instaltions. The Main reason why its not the best solution is because in the form its currently public it needs some manual work for each release, i've made some changes to improve the workflow but there is still full AL-Go Integration missing. |
Question
Currently, the missing dependencies for the AppSource apps we're dependent on are retrieved from the Microsoft NuGet feed during running the pipeline. That is a fantastic addition for us, a real unblocker.
Another part, that still seems to be blocked, is creating local development environments on docker.
I would have expected that creating a local dev environment with localDevEnv.ps1 would have resulted in a development environment with those NuGet symbols included. That seems not to be the case. Is that behavior as expected?
How should we create local dev environments in the specific scenarios where we are dependent on an AppSource app? Is there f.i. a work-around to get this app from the NuGet feed and push it into docker environment during the creating the environment by localDevEnv.ps1?
The text was updated successfully, but these errors were encountered: