I have ACCIDENTALLY deleted the libs folder from CRXDE Lite (this is the folder standing near var, etc, apps, content... etc). How to rebuild it? new start of the server did not help. I hope somebody can help..
Start a fresh CQ instance
Open Package Manager (relative path: /crx/packmgr/index.jsp) on the new instance
Create new package and add /libs to its filter
Build and download the package
Open Package Manager on the damaged instance
Upload & install package
If you want your current CQ instance, then, in a new folder copy AEM jar and start it in different port number(say 4503). Once start go to package manager create a package by adding a rule with /libs and then download.
package manager url(port number) : http://localhost:4503/crx/packmgr/index.jsp
Once download, upload this package into your AEM instance running in 4502.
Related
Is there a version package manager like npm, maven, nuget, pip? I just want my asset store assets to be saved in one way and when I open the project from a different computer everything will be downloaded with ease. Unity has a "package manager" but as far as I can understand it just helps you get the packages into the "Assets" folder. So, I don't see there is no package.json all anything like that what has been downloaded and triggered to download if not found.
I am sure there is a way to do it but I don't know how.
Unity's package manager uses /Packages/manifest.json to store it's dependencies as a JSON array. You can just copy-paste the file from project to project to have all those dependencies available from the start. Alternatively, you can just copy the individual entries for certain key packages, and use the defaults for the rest.
Just be sure that the packages are compatible with each Unity version you're going to be using.
I am trying to make a package of a specific folder "/content/diagnostics/states" to migrate it to a different instance of AEM. but it's not being included when I try to build the package, the package manager is just giving me an empty "/content/diagnostics" folder. Any idea of whats going on?
See screenshots:
Figured it out, all the nodes were there in a hidden .content.xml file
i generally add any library from Nuget to my project like issuing this command
Install-Package Mvc3Futures
then i have seen everything related to that library just added in my project. some one told me that library can be added to folder and later we can add that folder to my project like this way tools > options > package manager - add your folder .
really i have no idea how we can add library to any folder from Nuget. if it is possible then please show me the way in step-by-steps. thanks
I cannot give you a step-by-step, but you can relocate/specify the place of the packages folder: Is it possible to change the location of packages for NuGet?. But this way all of your packages location will change, I don't think you can do that per package. During installation you can specify where you install the package from (but not to): http://docs.nuget.org/docs/reference/command-line-reference, see Install Command.
I have been using NuGet to manage my internally created assemblies for a few months, and it's working very well. I recently 'discovered' portable class libraries, which has also been great - until it's time to install the packages.
Say I have a PCL that targets .NET 4.5, SL5 and .NET for Windows Store Apps. I run nuget spec to create the .nuspec file, edit the values, package it up, and add the .nupkg to our internal feed. If I open the .nupkg file in the Package Explorer, I see one content folder under lib called portable-win+net45+sl50.
When I try to install the package from any compatible project in another solution, I get the following message:
"'Project.PCL' could not be installed because it is not compatible with any project in the solution. The package doesn't target any framework."
If I manually create the .nupkg in the Package Explorer, updating the version number, adding a lib folder for each targeted framework (not a portable folder) and added the Project.PCL.dll to each folder, I can add the package to the compatible projects in the solution. But to do this process every time I want to update a PCl is somewhat tedious (I had been creating a little .cmd file in the project root folder to quickly package and deploy).
Do other people have this problem? How can I package PCL's in the same way as other types of projects?
Note - I'm using VS 2012 Ultimate and NuGet 2.2
It sounds like maybe nuget spec doesn't work for Portable Class Libraries - that's worth starting a thread or filing an issue on the NuGet site.
However, you can also create a .nuspec file from NuGet Package Explorer. Just create the package as you already did, but then choose "Save Metadata As..." to save it as a .nuspec. Afterwards you may need to edit the source paths in the nuspec file manually, but you should be able to automate the creation of the package.
For me nuget spec and nuget pack worked fine with a portable project while creating the package and installing it on a compatible project.
Do you want to check if you have the latest nuget.exe (2.2), it can be downloaded from http://nuget.org/nuget.exe or can be updated by running nuget update -self
I'm reading through the nuget documentation and I don't completely understand how nuget works.
I have 2 third party dll's that I have been asked to turn into a nuget package, so that our local developers can just install them to a project via nuget. This would be something that we would host locally.
Does this mean I just create a project in vs and drop the dll's in the project or do I use something like the package explorer.
I apologize in advance if this is a silly question, however I am an absolute beginner when it comes to Nuget, etc..
Any tips would be greatly appreciated.
The simplest and fastest way to get a nuget package up and running is to just fire up package explorer --> create a new package --> drag and drop your dlls into the "Package Contents" area, it'll ask you whether you want the dlls in the "lib" folder, which you do --> create a bit of metadata about the package, ie give it a description and version and whatnot, and then just save it.
After you save it, you can then copy the .nupkg file to a shared location - the file system on a centralised server is fine if you have access to one, and then setup access to this "feed" (ie, the shared folder) in visual studio (tools --> options --> Package Manager --> Package Sources), thus:
Or if you want to host the packages over http you can follow the instructions here: https://github.com/NuGet/NuGetGallery/blob/master/README.markdown.
Other option would be to use Nuget.exe spec, pack commands to quickly create package.
More details here # http://docs.nuget.org/docs/reference/command-line-reference