-
Notifications
You must be signed in to change notification settings - Fork 241
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
Docs on how to handle NuGet Runtime Packages #3590
Comments
I will be working on NuGet when back from vacation |
Thanks! If I can assist somehow of give feedback just let me know. Enjoy your vacation. |
HI @lktraser , |
Hi Kamil, that's very good to know. I would prefer to have everything integrated and documented within BCContianerHelper but I will look at that module to validate my work. At the moment I think I can make everything I need work I just want to make it easier for all partners and make sure they all work to the same standards. |
Hi @kine and @freddydk, I would really like to push this forward. To make this easier could you give me examples using bccontainerhelper for the following scenarios?
Your support is greatly appreciated as always. |
… . instead of -
Describe the issue
Hi this is not an issue in the sense of it's not working but missing documentation or pointers to such documentation.
I'm trying to adopt the NuGet scripts for our CI/CD and had a really hard time figuring out how to run the scripts correctly for Runtimes to work as intented. I'll include my script below because I need someone to tell me if I did this right or if I'm missing the obvious easy path I should have taken. I worked based on the slides from the BC TechDays but even with that information it still took me hours to get it right. I don't think such a fundamental thing should be this hard so we make the barrier of entry lower for better adoption rates.
My proposal would be to A) Write a post for Freddy's Blog on how to Push and Pull Runtimes with NuGet and B) include examples for runtimes in the documentation headers of the Push and Pull Scripts. Some general guidelines on how to setup Feeds, (prelease, release, runtimes, internal, external would also be appreciated)
I would really like to see large scale adoption of this technologie but handling runtimes is still a big part of that and needs to be easy. Ideally there should be a cmdlet/parameter that just does it correctly out of the box.
I've used the slide below to get this far. Is it correct that runtimes can only be pulled with 'Download-BcNuGetPackageToFolder' because 'Get-BcNuGetPackage' doesn't explore the dependencies and therefore will never find the actual apps?
Scripts used to create container and cause the issue
Pushing Runtimes:
Pulling Runtimes:
Screenshots
![image](https://private-user-images.githubusercontent.com/76940360/346111561-c03eeeb4-a7ad-4d10-8cbd-c90785dfd242.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQyNDkwODcsIm5iZiI6MTcyNDI0ODc4NywicGF0aCI6Ii83Njk0MDM2MC8zNDYxMTE1NjEtYzAzZWVlYjQtYTdhZC00ZDEwLThjYmQtYzkwNzg1ZGZkMjQyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODIxVDEzNTk0N1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWVkNDkyYTk0YTQ3NTY0ZDFiMmVjNGU3MDAwMGNiZjUyMDk0ZmFmODU3NTNhNDQ2NTA5MmNkZDZmNGJmYWNhZjMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.UY7E8XF_-mzXnu2AQx4TX5kB2MYUk1dT0kmntkbBMWo)
The text was updated successfully, but these errors were encountered: