generic.xaml not being re-packaged when modified - c#

What I have installed...
Windows Vista Ultimate Service Pack 1
Visual Studio 2008 Service Pack 1
.Net Framework 3.5 Service Pack 1
Silverlight 3.0
My First Problem...
I modify themes\generic.xaml and save the file and run the project and the changes I just made in themes\generic.xaml are not inside the assembly. I have used reflector to see what is in themes\generic.xaml and it is the previous version of the file.
Second Problem...
Upon realising this was happening I decided to test with modifying a C# file and I get the same problem - on compile it does not recoginise the code changes.
Note:
Before building all changes are saved via Visual Studio Option "Project and Solutions"->"Build and Run".
Using Local IIS Web Server
What I have tried...
I uninstalled ALL Silvelight, .Net Framework and Visual Studio components and re-installed only to have the problem re-occur.
Update 1:
Looks like the XAP file is not being updated. Just worked out this is only a problem when using F5 (Start Debugging) not when doing a Build Solution(Ctrl - Shift B or F7).
ANY suggestions welcome !

I finally worked it out and I am almost embarrassed to say what the solution is.
In Visual Studio 2008 goto Tools->Options->"Project And Solution"->"Build and run"
Turn OFF Option "Only Build Startup Projects and dependencies on run"

Related

.NET core SDK cannot be located vscode unity c#

my problem
I am on windows 10 I tried reinstalling .net multiple times and re installed vscode i am really despreate for soloutions now
Probably an issue with your .csproj. If you are on windows I cannot recommend enough for you to switch to Visual Studio. Everything is integrated, and trust me. Visual studio code will run into these types of problems every 5 minutes, where visual studio will not. If you are using unity I remember having to change “targetting packet” in the .csproj to 4.7.1 every time I loaded visual studio code. If you are not using unity, make sure you have run “dotnet new console” and “dotnet restore”.
Check your project file and take a look what kind of .net version is used there. Then look for that version in microsoft .net download page

Error during building application with Fody and Costura via VS 2019 : Binary is being used by another process

I have a C# Console application that was developed in different machines. In this application, we chose to use Fody, because it's the only thing we found that would embed all external resource dependencies (any extra class libraries) into a single executable for our application.
Environment Detsils:
Visual Studio Version: 16.9.2 (Professional 2019)
Type: Console application
Framework: .Net Framework 4.5
Fody Version: 4.2.1
Costura.Fody Version: 3.3.3
While this application worked without any issue in one machine, it starts giving trouble to another machine. We need to get this work on both machines as we need to cover lots of work. We have compared the two environments but couldn't figure out any difference.
the behavior of the issue is as below,
The first time when I clone and build a solution it goes in a
never-ending path and I have no other option other than end tasking
the visual studio.
And I observe that MSBUILD is occupied by something and I cannot end
task it
The second time when I start the solution and build it, I am getting
the following error.
Severity Code Description Project File Line Suppression State
Error CS2012 Cannot open '<<obj folder path>>\Debug\Binary.exe' for writing -- 'The
process cannot access the file '<<obj folder path>>\Debug\Binary.exe' because it is being
used by another process.' Binary.exe <<project path>>\CSC 1 Active
I had to restart the machine to remove the obj folder. And once it is removed Same above behavior repeats.
I found below a similar question below thread,
Error during building application with PropertyChanged.Fody
But it seems like this feature is obsolete in the latest Visual studio as per the below question.
Disabling Visual Studio hosting process on Visual Studio Community 2017
Further, I have tried to set the environment variable as explained in the below thread as I thought its somewhat relevant. However, it doesn't work as well.
https://github.com/Fody/Fody/issues/537
I must use these Nuget packages in my solution. Highly appreciate it if someone can share some thoughts to sort out this issue

Creating an ASP.NET Core project

I want to create an Asp.net Core project with Visual Studio 2017 Community but the Solutions explorer says that I have (0 projects).
I tried selecting an empty project, web application, web application (Model-View-Controller) but the Solution explorer still displays (0 projects).
When I go-to Debug I see the "Attach to Process" option. There is no option to start of course since I have no projects.
What could be the issue?
Have you installed everything correctly? To verify this, open a normal cmd and just type 'dotnet'
Only if the command runs, printing out information about how to use dotnet, you're good to go.
Have you installed the correct .NET SDK? What version of it? Make sure the version is compatible with the version of visual studio you have installed.
Follow this link for step by step setup instructions:
https://www.c-sharpcorner.com/article/getting-started-with-net-core-on-visual-studio-2017/
This could be the same problem, but I had the same issue during College once but this time I had the support for the web components, so I went back to the installation and repaired it. It downloaded the missing files and it worked again and it took a while.
Let me know if that works or not.

Can you really run your vs 2012 app on Win XP? and how?

I've seen a lot of thread(s) regarding with their visual studio 2012 app to run with their Win XP-32bit. Some says you need to change your target framework to 4.0 below, install the same framework to target pc, then make sure you include your publish-prerequisite to your target framework.. but it doesn't work on my case ,it always says that my app is not a valid win32 etc.
my last resort would be compiling my vs 2012 app to vs 2010 but i dont think it's a good idea though.
temporary solution:
for future reference(if the update solution dont work for your case):
build your window app(c#) to framework 4.0,
copy the files on your Debug Folder and paste on target pc
Run the .exe
Voila!

Visual Studio 2013 sp1 hangs when trying to debug ASP.NET web site?

Recently, Visual Studio 2013 started hanging again when trying to debug/trace an ASP.NET web site. The site was created with WebMatrix 3 but I don't think that is relevant.
VS2013 opens the web site Solution. It takes a really long time to load up. Once it does load up and I run the project, it hits my first breakpoint and then the IDE Window quickly shows "(not responding)" in the title bar and the IDE is now hung.
This happened to me a long time ago and the root cause was needing to set the "use 64-bit IIS" option as indicated by this SO post:
Visual Studio 2013 crashes and restarts every time I run my test solution
But I triple-checked and I do have the 64-bit option checked. What can I do to fix this?
What worked for me was resetting visual studio. I got the suggestion from http://www.vosseburcht.com/?p=69
See this blog in the issue. It basiclly says to make sure "show all files" is selected in the solution and check for any folders that don't belong that are not part of your project/solution.
The problem resurfaced again a few days later and I finally figured out the problem with my uncooperative debugger. I have a folder containing approximately 20,000 images that are not included in the Visual Studio web project but are sitting in a directory in the web site. I had turned on "Show All Files" in Solution Explorer to add some script files into the project. When "Show All Files" is off, F5 (Start Debugging) works like champ. When "Show All Files" is on, Visual Studio becomes unresponsive. In reality it is not "frozen" but simply taking a very long time to process those 20,000 image files.
For me, it was a folder created called backup, which was a backup of the site (created by VS). I deleted the folder in question and the site loaded for debugging.
It might be caused be some extensions in Visual Studio, I was facing a similar problem when degbugging asp.net websites. Try running VS in Safemode: devenv.exe /Safemode. In my case it was caused by Multilingual App Toolkit extension, after uninstalling it, debugging ASP.NET websites works once again.
In my case, I was able to solve it by running it as an Administrator!
Don't know why, couple of days back it was working fine, suddenly it started to freeze when trying to debub web app!
Hope it helps someone!
BTW: I am running VS2013 Ultimate, with Update 4
In my case it's the IntelliTrace that causes problem. I need to disable it https://msdn.microsoft.com/en-us/library/dd264948(v=vs.100).aspx
I have the same situation and "solved it" in a very particular way: Rebuild the solution and run it without debugging (Control + F5), then go back and debug it the normal way.
I was having a similar issue, and I found the following error in Windows Application Event Log that corresponded to the problem:
Application: PowerShellToolsProcessHost.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.Serialization.InvalidDataContractException
...
So I removed PowerShell Tools for Visual Studio extension, and the issue went away. I am using Visual Studio Ultimate 2013 Update 5.
I had this problem while writing an Excel add-in.
Not being a web app I was pretty sure that checking the 64 bit IIS Express option would make no difference, but it did!
I have no idea why, but it runs in debug ok now :)
I had to install Windows Management Framework 4.0
My solution was to remove all the .bak backup files generated by DevExpress ProjectConverter when I had upgraded to the new DevExpress version.

Categories

Resources