I am using Enterprise Architect from Sparx Systems. I have a 1 model project and several packages are version controlled. I am using SVN to check in these model/packages.
I would like to understand what would be the best way to add a package tree to existing package tree which is already version controlled?
For Example, I have following structure which is already version controlled -
Model
-- Package 1
-- Package 2
-- Package 3
Now I would like to add another set of packages
Model
-- Package 1
-- Package 2
-- Package 3
-- Package A
-- Package B
-- Package C
The package A (& B and C) is imported from another project, and it already exists. All I want to do is create these new tree under Version Control setup, so that I can check in new tree under Package 1. Is there an easy way to do this?
Just follow these steps:
Check out Package 1 (allows addition of new packages/elements).
Import Package A (and its children) into Package 1.
Make Package A version controlled (since you want it to be on its own).
Check in Package 1.
Related
I used NuGet Package Explorer (for the first time) to create a .nupkg to share with others. I have one DLL that targets NetStandardLibrary 2.0,
But when I try to add the package I receive the following error:
Could not install package 'iCANMVCSDK 1.0.0'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.7.2', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
I thought that by using NETStandard 2.0 it could be installed in any .NET app. I also tried adding additional assemblies:
I rebuild, repackage, and I still get the same error. What am I missing?
I tried editing the project file like this:
<TargetFrameworks>netstandard2.0;net472</TargetFrameworks>
When I try to build after adding net472, I receive the following error:
The type or namespace name 'Http' does not exist in the namespace 'System.Net'
What really makes no sense to me is that I can add the DLL directly into the project (the one that targes NET 4.72) and it works as expected. The problem is when attempting to install it as a NuGet package.
I want to be able to update my system by installing packages created by Yocto instead of installing the whole image created by it. The objective is to update some software without affecting the system configuration. However, I want to avoid updating a package without updating other runtime dependencies that changed to avoid leaving the system in an inconsistent state.
The approach that I'm following until now is to set version restrictions to package. Suppose I have a layer with recipes A.bb and B.bb that creates packages A and B. I'm using RDEPENDS on A.bb to set package B as a dependency of package A as follows:
RDEPENDS_${PN} = " B (= hard-coded-current-version)"
where hard-coded-current-version is something like 1.1-r1. However, what I want is something like:
RDEPENDS_${PN} = " B (= parametric-current-version)"
where parametric-current-version would be something like ${PE_B}.${PV_B}-${PR_B}.
How do I specify a version restriction of package A to be the current version of package B?
I developed a nuget package "nuget_X" installed on a project "project_1".
I have a second project "project_2" that reference "project_1".
If "project_1" is published as nuget package "nuget_1", I can force "project_2" to reference "nuget_X" by declaring "nuget_X" as dependency of "nuget_1"
But "project_1" is referenced as "ProjectReference". So, how can I configure "nuget_X" or "project_1" to force "project_2" to install "nuget_X"?
PackageReference on Visual Studio 2017 don't allow to force nuget of dependency to be installed when using ProjectReference. But it allow to produce an acceptable equivalent result. for more details, see comments.
I've imported the Hangfire Source code from Github into my existing VS 2013 solution. When I attempted to build all projects within my solution, I get several errors:
Error 6 The type or namespace name 'Dapper' could not be found (are you missing a using directive or an assembly reference?) C:\Users\Jerry_Dev\Documents\GitHub\Hangfire\src\Hangfire.SqlServer\SqlServerDistributedLock.cs 20 7 Hangfire.SqlServer
In Package Manager, when I do: "Install-Package Dapper", it says
'Dapper 1.38' already installed.
Hangfire.SqlServer already has a reference to 'Dapper 1.38'.
I see Dapper dot net installed in my Manage Nuget Packages Window in my Hangfire.SqlServer project
We don't store the packages folder under source control to reduce the source code size. Hangfire uses Automatic Package Restore in Visual Studio instead of obsolete MSBuild-integrated package restore. The Automatic Restore downloads missing packages automatically on each build, but it works only with NuGet ≥ 2.7, so you have the following options:
Update NuGet to the latest version
Please see the official docs.
Run the build script
Go to the root Hangfire directory and run the build.bat file. It will automatically restore all the missing packages.
Example:
Nuget package A is a set of code snippets (it does not contain an assembly).
Nuget package B is a normal assembly and it is using package A - just for internal means.
Question: What can I do, to avoid, that package A is also installed, when somone installes package B?
Found something in documentation of nuget:
Starting from version 2.7, the pack command will ignore entries in the packages.config file which have an attribute developmentDependency set to true and will not include that package as a dependency in the created package. For example, consider the following packages.config file in the source project
That seems to solve the problem.