I just started using Artifactory for my pet project and I want to configure it to support nuget. I know that Artifactory Pro supports nuget but I am curious if it's possible to do that without using Pro.
It is not possible. You might consider applying for an account in oss.jfrog.org (if your project is popular and open-source).
Related
We have an on-premises Azure DevOps 2019 server, with build pipelines for numerous .Net 4.x solutions that our small team maintains using VS2019.
The team is about to upgrade to VS2022, and at some point I would like to migrate some solutions to .Net 6. Can DevOps 2019 build .Net 6 solutions, and if so what changes are needed to support this (such as presumably installing VS2022 on the server)?
Will those solutions' build pipelines require any changes or should they continue to work as-is? They don't contain anything too clever, with steps such as: NuGet restore, build solution, run unit tests, NuGet pack & push. (The build pipelines are managed via the web GUI, not YAML, if that makes a difference).
Some solutions will remain .Net 4.x, so the server will still need to support (build) these.
You should just need two things:
First you have to install the corresponding SDK for building the apps (see sdk download - Build apps - SDK) on your build-agents.
(Optional) Add or modify your set SDK Task in your pipelines (see use dotnet core task).
One more hint, you don't need to install a whole VS on the server. The Build-Tools are enough (VS2022 Buildtools preview).
I have a few tools that I would like to use during a build. For Azure DevOps I tried putting them in a Universal Package. This works great for Windows but on Linux and Mac the file attributes are not preserved, specifically the execution bit. Is there some way to preserve the attributes with a Universal Package, or is there another tactic I need to take to use tools during a build?
I need something that is not done by a pipeline task because it needs to happen on developer's boxes as well. Pulling just about any sort of repository or package is viable.
How to preserver file attributes with universal packages in Azure DevOps?
I am afraid there is no such way to preserver file attributes with universal packages in Azure DevOps.
It is precisely because of the non-preserving properties of universal packages that it may be used to store different types of packages other than the widely used ones like NuGet, npm, Maven, or Python packages.
To use the tool package for Linux and Mac, you could consider to use HackPorts and Kali Linux.
I'm setting up my first pipeline job in azure devops. My C++ application uses the QT framework with qmake to create the make files. It also makes heavy use of the QT framework.
I'd like to use the Microsoft managed ubuntu server. How do I get the QT open source framework and tools installed on the build server? Or, do I have to use a self-managed server?
You can find all the supported Software packages in Ubuntu 1604 image at here. So as per the official docs QT is not supported by the Ubuntu hosted agent,which means you have to use your own custom agent for the build.
I've created a simple Azure Mobile Services project and added the nuget package for MongoDB (package id is mongocsharpdriver).
The version I added is 1.10.0
When I deploy the project I get the following error:
"Found conflicts between different versions of the same dependent assembly 'MongoDB.Bson': 1.10.0.62. Please change your project to use version '1.9.2.235' which is the one currently supported by the hosting environment."
It seems like the Dlls from the package I've added are conflicting with an older version installed by default in the cloud environment.
Is there a way to get around this problem?
(While trying to figure out whats wrong I installed the nuget package WindowsAzure.MobileServices.Backend.Mongo which can't be installed because it requires mongocsharpdriver(=1.9.2) and dose not allow me to use my newer dlls.)
It seems I'll have to wait for microsoft to update the dll in Azure:
Can we use NuGet packages in developing WinRT Metro style applications using XAML/C# or HTML/JS/CSS?
NuGet currently supports WinRT libraries for deployment in your project for .NET 4.5 -- we're working with the team to get greater support there as well.
Here is a 2 parts articles on how integrate Nuget Dev with WinRT component :
http://blogs.msdn.com/b/mim/archive/2013/08/27/packaging-a-windows-store-apps-component-with-nuget-part-1.aspx
http://blogs.msdn.com/b/mim/archive/2013/09/02/packaging-a-windows-store-apps-component-with-nuget-part-2.aspx
I Hope this could help you !
Sebastien