Using Xcode File/Swift Packages/Add Package Dependency menu option I am able to add a local package by giving the url as file:///Users/saran/Desktop/Temp/NetworkUtility
Since it takes absolute path in my machine, would affect team development when a team member checkout my commit.
Is there a way I can mention the file url as relative path to the depending local package.
Having my consuming app in a folder sibling to NetworkUtility
I tried file://$(SRCROOT)/../NetworkUtility, but only getting popup "An unknown error occurred"
Not sure from which directory it is trying to resolve.
Any help is much appreciated.
Related
I have build a nuget package at published it to a nuget.server site. But when I try to use the package form the server the .targets file from build folder is not in the file. But if I use the package from a local folder it works as it should. How do I get it to work ?
If i look in the package in the folder on the server it looks ok.
It's not clear to me if you mean using (referencing and restoring) a package, or building (packing) a package.
If the problem is with packing the nupkg, NuGet requires the props and targets files to have specific filenames in specific folders, but if you got it to work at least once, you probably already know that. If this is not the problem with packing, you need to give us more information because not using the correct filename convention is the most common problem and I can't guess what else the problem could be. In particular, if the package is being packed differently on your local machine compared to when it is packed on the server, it means there is something different between how you pack on the two computers, so we need more information about how the build and pack work with your project.
If the problem is with using (restoring) the package, there are a few possibilities. My best guess is that you once had a package without the targets file working correctly, and you restored the package on the server. By design, NuGet packages are immutable which means it's invalid for the contents of a package (same ID and version) to change. This allows NuGet to download the package from a remote feed once, save it in the global package folder (not a cache; they never expire) and the next time NuGet needs to restore the same package (id + version) it uses the one in the global package folder, it does not download again. This means if you once built a bad nupkg and restored it on a machine, then fix the nupkg and kept the same version number, that machine will never get the fixed nupkg. You need to delete it from the global packages folder. I'm not 100% sure, but I think if you have a local file feed and you restore a project that uses packages.config, the nupkg does not get saved in the global packages folder, so doesn't have the same problem. In short, I think the problem is that you changed the nupkg contents once without changing the version number, and one of the machines has the old copy in its global packages folder that it keeps using.
If that's not the problem, the next most likely cause is that the nupkg on the server feed has different contents to the nupkg in the local feed. I've never used NuGet.Server, but some nuget respositories (like nuget.org) do not allow overwriting nupkgs. So, if you pushed a nupkg to your server, fixed a problem in your nupkg without changing the version, then tried to push again, the second push might have failed.
In summary, your question doesn't provide enough information for us to help you, but I wrote about the most common issues above. If it doesn't help, you need to provide us with more information. An example of the problem is the best way to give us enough information to help you.
Everytime I upload a package on my QA server via Package Manager, it keeps loading it for a long time and then throws an error saying "package file parameter missing"
The error logs show absolutely no activity regarding the package.
This happens for both code packages (/apps/...) and content packages (/content/...)
Make sure your server has a tmp (linux) or temp (windows) folder accessible to the AEM process with full permission. This error occurs when the aem process cannot find the temp folder which it uses to temporarily store packages when they are being uploaded.
I'm programming a client side applications using SharePoint Designer 2013.
I want to change to VSCODE since it supports a lot of extensions for some Javascript library like angular, jQuery. And because of the Chrome/Node.js debugger extension.
But when I try to start any Debugger, I got the error:
Unable to create 'launch.json' file inside the '.vscode' folder (Error: UNKNOWN: unknown error, mkdir '\\servername\DavWWWRoot\sitename\Style Library\.vscode').
I get this error because it's impossible to create a folder in SharePoint where the name starts with dot.
So there's a possibility to change the name of this folder or the file location to any directory in my local computer?
No, it's not possible to move/rename that folder. VS code is a tool that bases project management on folder content. So it is essential that the project settings reside in the folder being managed.
You can move the "extensions" folder, but unfortunately not the argv.json (so the ".vscode" will, at least be recreated on vscode launch)
https://github.com/microsoft/vscode/issues/17691#issuecomment-559234574
I hope that'll finally change sometime .
https://github.com/microsoft/vscode/issues/3884
https://github.com/OmniSharp/omnisharp-roslyn/issues/953
I am working with veins. I needed to change the default behavior of BaseWaveApplLayer. Rather doing in file changes, I created a second application file with the name MyApp. I added MyApp.cc, MyApp.h, MyApp.ned files. Then I duplicated TraCIDemoRSU11p, and added files for TraCIDemoRSU11pEnhanced. Now in .ini file when I changed *.rsu[*].applType to point to "TraCIDemoRSU11pEnhanced". It compiles fine, but when I try to run it, generates the following error:
Submodule appl: no module type named `TraCIDemo11pEnhanced' found that implements module interface org.car2x.veins.base.modules.IBaseApplLayer (not in the loaded NED files?).
In MyApp.ned file it is declared to be of type IBaseApplLayer. I tried setting ned-path parameter in ini file, didn't resolve the problem. In veins project properties, NED source folder is checked. Do I have to add the ned path for the newly created application file, somewhere?
Try using the cookiecutter package (https://veins.car2x.org/tutorial/#newprojects) to create new applications that use veins instead of copying and pasting files:
Use pip to install the package (https://github.com/cookiecutter/cookiecutter)
Then follow the steps in (https://github.com/veins/cookiecutter-veins-project/blob/master/README.md) to create the new project; following the prompts that appear.
This will create a new project that uses Veins and has the application layer-related files for you to update according to your application with no errors.
So I made a repository for an app and everything in Xcode is setup. Now another person tries to pull it and that works fine until this message appears: The File "UserInterfaceState.xcuserstate" could not be unlocked, unlocking failed for an unknown reason.
The project uses the Google Maps API and gives the error: "GoogleMaps/GoogleMaps.h" file not found. Even though the project is a direct clone, it works for me but not for him.
For the error of "GoogleMaps/GoogleMaps.h" file not found.
You may have not set the path properly. For setting right path do following steps:
Go to Targets -> Build Phases -> Link Binary With Libraries
Click on + option
Select the GoogleMaps Framework. If you have added it from outside than go there & select it.
Go to Targets -> Build Settings -> Header Search Paths
Remove the older path of Google Maps API from it (keep new path don't remove it)
For "The File "UserInterfaceState.xcuserstate" could not be unlocked" issue
refer this : http://www.meetup.com/818-iOS-Developers/messages/boards/thread/20469352
You probably corrupted the file by using Git, that, or you overwrote a locally saved file with something from the cloud. Try recreating the project without using Git, and see if it works.