In company we are using Visual Studio Code for developing TS projects. We often use file dependences for development. From time to time occurs problem with file dependences when they are like:
"#companyName/subModuleServiceWorker": "../../companyName%20subModule/ServiceWorker"
Usulay it's works fine, but sometimes symbolc link in node_modules is broken. After change directory and dependency referenece from "companyName**%20**subModule" to "companyNamesubModule". After npm install everything is works fine.
All team working on Win10, using same dependecy and for most of time it works fine. In addition when some team member has problem, others working without any problems.
Is there another solution than change directory names on all team members work stations?
Related
I am trying to run the Q# Teleportation sample. I cloned from the official Microsoft GitHub Repository, restored all dependencies, I have the Q# Development SDK installed also. The problem is when i run it the first time it worked now i tried running it again and i get this error.
TeleportClassicalMessage' does not exist in the current context. I run it for the last time and it worked even with the Error. I have by the way set up TeleportationSampleas my startup project.Is there any reason for this behaviour?. I am new to Q#
Even with the red Squiggly the Application run after another try.
I solved this by deleted the bin and obj directories then run again.
my experience: Quantum Program The name 'BellTest' does not exist in the current context
From my experience (playing with slightly modified sample BellTest code), Q#-generated classes are properly referenced in C# only after you rebuild project (meaning dotnet build). So if you make some changes in names that are visible on the C# side, try building it and reference issues should go away.
This was tested using VSCode on Windows 10 x64, .NET Core v 2.1.103
I ran into some issues yesterday. All of a sudden I couldn't build my C# solution. At first I thought it was related to us recently mixing project.json files with csproj/package.config files which resulted in some issues with resolving references, but the steps I have taken seem to rule this out.
The build is failing (all 23 projects) with no error messages at all. The build is successful for all other members of my team. The steps I have taken include:
Clean solution
Delete packages folder for solution
Delete bin/obj folders
Delete all temporary/non-mandatory files (.user, .DotSetting, etc)
Delete ASP temporary files (in windows/.net folder)
Delete temporary files in AppData/(Local/Roaming)
Delete temporary files in ~/.nuget
Check out an older guaranteed working branch
Uninstall all VS extensions
Reinstall VS2015
Delete and re-clone the git repo
After all this I tried to create a new solution with an empty class library project. This also fails to build with no error messages.
At this point I am getting more than a little frustrated. It seems like the only thing I haven't tried is to find and delete some obscure registry keys or just reformat the hard drive.
EDIT: I have managed to build a C# project using MSBuild from the command line, although this really doesn't seem to be that significant since the problem obviously isn't in the code since even a new empty project won't build.
I got it working now, and while I am not sure exactly what step did it, the most recent steps I took were:
Reboot
Run a repair on VS2015
Reboot again
Delete all temp files again
Clean solution
Delete packages
Open solution and restore packages via nuget package manager console
Build
All steps were probably not necessary, but I have no idea what the minimal steps required are since I still don't know exactly what broke. I hope the list I established can be of some use to people with similar issues, since at least some of the steps should help.
I just installed the Microsoft Multilingual App Toolkit for my windows application.
Target framework 4
The installation went well.
But than when I tried the project I get this message:
Could not find file 'obj\Release\qps-ploc\Appname.resources.dll'.
The error message is correct, the file is not there, even the folder it should be in, wasn't generated.
I manually created the folder and tried to build the project, with no luck, same error.
So I thought, lets add the wanted languages, and remove the psuedo language.
But that wasn't possible, and now I have 3 error messages.
One for each language.
Than I tried to Rebuild and Clean the Solution, but both didn't solved the problem.
Also a google search didn't gave me a solution, which can also be a problem of non native english search terms.
So my question is, how can I generate the required resource.dll?
EDIT:
I just copied a dll file to the folder, and renamed it to the needed filenname, now the project is building again, and I'll have a look for other problems and if it really works.
But surely, there must be a right way to achieve this?
I am creating my own site template for SharePoint. Everything has been going fine, building fine, deploying fine. For unrelated reasons, I needed to reboot my development server. I then made an update to my custom.xsl file and attempted to deploy in Visual Studio 2012. Even though it says Deployed Successfully, My changes are not reflected in SharePoint, and I received the error in my question. Additionally, I am getting 32 warnings that this or that attribute is not declared, even though I made one small change (added a link for testing) to the blog.xsl I copied my custom .xsl from. I reverted all changes, attempted to deploy again, but cannot get past this error now.
Any ideas where to start looking to solve this? Needless to say _layouts is NOT in the root of the C drive, but it the 14 hive under Templates.
I recently updated a project in my solution to use MVC 3 instead of MVC 2.
Ever since doing that, and although it compiles in my machine, I get the following error in the server:
/MyProject.csproj/global.asax (1,0):
errorASPPARSE: Could not load type 'MyNamespace.MvcApplication'.
Any ideas?
It compiles and works ok in my machine.
It compiles in the server if I open it in a VS.NET 2010.
It compiles in the server via msbuild.
UPDATE:
The exact command that fails is this:
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_compiler.exe -v /MyProject.csproj -p c:\cruisecontrol\trunk.project\checkout\Solution\Project -u -f .\TempBuildDir\
If I open the VS.NET 2010 in the server, compile it once manually, the command then runs ok.
The problem is that my CC.NET deletes everything and then checks it out from source control from scratch, so this approach doesn't work for me. Although it's interesting because it's weird.
UPDATE 2:
I was able to reproduce this locally, so it's not a problem specifically in the CC.NET server.
Could someone try to reproduce it?
MVC 3 application with razor (although I doubt it'd make a difference), run aspnet_compiler on it, and see if it fails with that error. Just close VS.NET as soon as it creates the solution and the project.
This does not happen if I compile it at least once with Visual Studio
If someone is kind enough to try it, I can rule out a problem in the 2 machines I tested.
Apparently aspnet_compiler.exe required that the /bin directory exists, that's why building it once with vs.net fixes the consecutive compilations using aspnet_compiler.exe.
I don't know why this worked before changing my application from mvc 2 to mvc 3, but I fixed it by changing a property in the .wdproj file
From
<SourceWebPhysicalPath>..\..\Project\</SourceWebPhysicalPath>
To
<SourceWebPhysicalPath>..\..\Project\bin</SourceWebPhysicalPath>
Source