Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 5 years ago.
Improve this question
I have little problem because I'm trying to run a powershell script in a console but Visual Studio is telling that Console.WriteLine() or Console.ReadKey() doesn't exist
Add this to your class:
using System;
The using statement is usually included as default, but if you use tools to "Remove Unnecessary Usings", then it may get removed. If you then later add code that requires the System namespace, then you have to include it again.
You could probably also fix the issue in by placing the marker on the Console in the Visual Studio code editor, and press Ctrl + '.'(period), to open the Quick Actions and Refactoring context menu.
Related
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 6 months ago.
Improve this question
We recently upgraded to 2012 Visual Studio 11.0.50727.1 (update 5). We need to keep 2012 because in later versions, the C# statements do not work (like obj["Click"] ()).
So when I brought it up I got a message that SccProviderPackage did not load correctly (see image). IT said I could probably ignore this, as it is not used.
But then when I opened my projects there was a problem. I can still see the Solution Explorer on the right (see image). But on the left where there used to be the tests I can run there is nothing. Not even a menu. I looked through the View menu to see if there was a way to show it, but I could not find anything.
Could this be a problem from that error, or some other kind of error?
BTW this is on Windows 10.
error loading
I needed to do a Ctrl + E, T to get the menu to appear
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 2 years ago.
Improve this question
I created a Windows Installer package a few years ago and now I found out that there is a typo.
I can't find the source code of this dialog to fix this issue.
Is it maybe a known error in the "wix-toolset" or is there a way to fix this error?
That dialog isn't part of WiX. You need to find out where it's coming from (custom Windows Installer dialog or custom action) and fix it there.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 5 years ago.
Improve this question
So I recently started using Visual Studio 2017 for my C# class.
I recently created a code that I saved and wanted to see if it work properly. So I build the solution and it went successfully. I looked up the application(exe) file and opened it but immediately the command prompt would close so i don't even get a chance to view that the code worked. Is there anything I can do so I can view the code in the command prompt and properly run it so i can see it work correctly.
Any Help would be greatly appreciated!
Quick Note: I tried doing ctrl + f5 key to run the program but for some reason it doesn't work on my laptop nor do anything
It sounds like the program actually finishes and therefore closes. Adding a
Console.ReadLine();
at the end of your program will require an enter key press before closing.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 7 years ago.
Improve this question
My code (C#) behaves differently (in specific: a method does not work in debug-mode but in release-mode and for another method the other way around) when I#m running it in debug- and release-mode (I'm using Visual Studio 2013 Ultimate). This problem has never occured to me before so I'm really confused!
Thanks in advance,
Nils
PS: I didn't post any code because I don't think it has anything to do with it - but if so I will of course.
Can you possibly see something like this in code?
#if DEBUG
// Your code
#endif
or
[Conditional("DEBUG")]
[DebuggerStepThrough]
If so, it will only run in debug mode.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 8 years ago.
Improve this question
I have recently started C# programming, after having a crack at making my own calculator using Windows Forms i have started getting this error message :-
Error 1 Could not write to output file ' c:\filepath\obj\Debug\My
Calculator.exe' -- 'The process cannot access the file because it is
being used by another process.
I have tried turning off my anti-virus
It isn't already running
Im not very experienced so i don't know how to write my own code to bypass this error and can find anything useful information on the internet.
Step by step help tips are always welcome :)
edit: i thought it was too obvious too write down but the program i am creating isnt running (even in Task Manager) and im am using VS 2012.
This problem usually happens when you try to start the program but haven't closed it after you started it last time.
Things to try:
Close your program (the forms you developed)
Restart Visual Studio
If nothing works, open task manager and look if your program is still running even if you can't see it on the screen.
You can find out which process is using a file by using this tool from Microsoft:
http://technet.microsoft.com/en-us/sysinternals/bb896655.aspx
Further to Cosmin's answer, you may have the file in your clipboard, try copying another unrelated file to ensure that the exe is not in your clipboard.