XNA on VS 2010 crashes on debug - c#

If I want to create a new XNA 4.0 project in Visual Basic C# 2010 and debug it VS2010 just stops working. I dont get an error message and it doesnt turn white and says *.exe has stopped working. Moving it doesnt work and the 3 upper left buttons every program has dont respond. Closing or minimizing it by the task bar just throws a windows beep sound at you.
When looking at the Task manager I can see that the project I debugged is opened in three processes. If I task kill VS 2010 by the task manager 2 of these 3 instances of the project remain AND CANT BE CLOSED BY THE TASK MANAGER (It's not a graphical bug they get displayed after restarting the task manager too)
Note: That only occurs when creating a NEW XNA project. Creating new normal VS projects works fine. Old XNA projects still can be debugged too.
I tried:
Uninstalling XNA 4.0 Refresh
Uninstalling XNA 3.1
Reinstalling XNA 4.0
Reinstalling VS 2010
(In that order)
None of the above worked...
I also searched for that problem on multiple forums but didn't get a useful answer.
What can I do? Or was something I described unclear? If so please ask.

Related

Timed Out, Error when loading Form Design on Visual Studio

I am running Visual Studio on a Windows 11 VM with Parallels on an M1 Mac. Visual studio works perfectly when creating a new project but when I try to open an already created project with a different .Net Framework version than 4.7.2, I cannot open the Designer for the forms in the project.
I tried changing it to 4.7.2 from properties and manually changing in .csproj but this will generate other errors and eventually cause problems to other people opening the project (as it is shared with GIT).
Running the project will not cause problems, the app builds perfectly.
How could I try to solve this problem?
The full error is: Timed out while connecting to named pipe.
Thank you.

Winform cannot be edited without fully breaking layout (2017 to 2015)

As I left home for a weeks holiday I decided to quickly zip+copy a project I have been working on from my pc to my laptop. It is a c# winforms application that I have been creating on my PC using visual studio 2017 community.
My laptop however uses visual studio 2015. If I just open the project on my laptop and run it, everything is fine. However the slightest change to the form (IE anything that causes it to save?) and when I run the application half my controls now anchor off the right hand side of the screen and are out of view.
I can restore the project back to working by replacing Form1.designer file with the original from my zip and rebuilding - but again any changes after that break it in the same way. The bizarre thing is the form looks absolutely perfect IN the designer, both when opened and unchanged and after changing regardless of how it looks when the program is executing.
Completely baffled and thinking I'm going to lose a week of leisurely work - any ideas as to what may cause this? I could try installing 2017 to see if its a going backwards problem but the free wifi at my location is.. lacking.

Visual Studio 2015 - Multiple Versions in Multiple Windows Won't Build

I use the Microsoft Recommended way of structuring my solutions:
https://msdn.microsoft.com/en-us/library/bb668992.aspx
Typically I work off the main branch, and occasionally I open a older release. When I'm working I often have the Main branch open in one VS window, and an older release open in the other, something like this:
Visual Studio Window 1 - Main Solution(Solution containing: Web Site with several other Main Class Libraries)
Visual Studio Window 2 - Release 2.0.0(Solution containing: 2.0.0 Web Site with several other Version 2.0.0 Class Libraries)
Often times when I have both windows open, Visual Studio becomes confused between the two of them. For example, I build the 2.0.0 version of my website and then attempt to build the main site, the main site build will fail referencing a missing object that clearly exists within the project but not in the older version(2.0.0):
(Reference exists in Main branch, but not in 2.0.0)
My work around to this issue is to close both Visual Studio windows and then reopen only the main branch, rebuild, and everything works correctly.
It appears as though Visual Studio is confusing the two projects. Is there a way to get around this issue without closing both windows?
Update 1
I've tested this on VS 2017 and it doesn't seem to be occurring, I've also changed my folder schema since I first encountered this behavior.

Visual Studio 2017 does not working - Always freezing and saying "it's busy"

Every time I trying to create some Xamarin project it freezees and when I try to click anyware in UI, pop ups a notification from Windows saying the the "VS 2017 it's busy" something like that. For task mananger still answers and runs normally. The same happens if go to Tools -> Options and try go to Xamrin category. I tried to explore other functions of the new IDE, same happens when I create a WPF project and try to access the toolbox with UI elements.
I created other kind of projects for test, and console projects and and the integration with Unity seems is working fine too.
I've tried repair the installation too but no success.
I tried to download the SDK and NDK through the VS Installer mentioned in other question but didn't fixed too. And what about the WPF toolbox, why is not working either?
UI is freeze
Try updating Visual studio 2017 from the installer,it worked for me. Thanks.

visual studio express 2013 stuck when creating project

When i tried to created a WPF application it gets stuck on "Creating Project" and an error message occasionally pops up
"
Microsoft Visual Studio Express 2013 for windows desktop is waiting for an internal operation to complete. if you regularly encounter this delay during normal usage, please report this problem to Microsoft."
I've tried to search for answers and disable my antivirus but to no avail. Would appreciate any help.
I had the same problem while working on an ASP.NET project; the only thing that worked for me was building a new project and copying and pasting the code.
(It took a really long time to build the new project for some reason.)
Restart your VS and/or your PC. VS 2013 is incredibly faster than 2010 but still has many bugs.

Categories