Modify readme.txt
This commit is contained in:
@@ -1,5 +1,24 @@
|
|||||||
|
Issue 1:
|
||||||
|
On initial check-in or doing a new pull, Git will fail with long file name issue
|
||||||
|
|
||||||
|
Add the following to registry (there's alreawdy a longpath.reg in the how-to folder file created so just run that):
|
||||||
|
"LongPathsEnabled"=dword:00000001 to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
|
||||||
|
|
||||||
|
Make sure Git for Windows is installed
|
||||||
|
Open command prompt in admin mode and run: git config --system core.longpaths true
|
||||||
|
|
||||||
|
-----------------------------------------------------------------------------------------
|
||||||
|
Issue 2:
|
||||||
|
|
||||||
|
If the solution folder is located in some long path, Visual Studio will not be able to extract Raytheon.Instruments.InstrumentManager.GeneralInstrumentManager.1.4.1.nupkg
|
||||||
|
to cache folder. Even if we manually move the DLL to the cache folder, Visuao Studio will not see it
|
||||||
|
|
||||||
|
Find a location where the path is not too long and it will build. So work out of there instead
|
||||||
|
|
||||||
|
-----------------------------------------------------------------------------------------
|
||||||
|
Issue 3:
|
||||||
If building for the first time after doing a Git pull, it will fail because there are a few packages that need to be built first and published to the "SolutionPackages" folder
|
If building for the first time after doing a Git pull, it will fail because there are a few packages that need to be built first and published to the "SolutionPackages" folder
|
||||||
since other projects that depend on packages in that folder.
|
since other projects that depend on packages in that folder.
|
||||||
|
|
||||||
So if the build fails, try building again until all the projects are built.
|
So if the build fails, keep building until succeeds. Takes about 5 tries
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user