Cannot publish because a project failed to build and Could not find file 'obj\x86\Debug\MyApplication.exe' Errors - wpf

I am striving to get the source of my issue but no luck. I did check almost all suggestions to fix this problem when publishing project (publishing using right-click, checked DevExpress is not installed).
-Regarding DevExpress the application have some of it's assemblies.
- Cannot publish because a project failed
- Could not find file 'obj\x86\Debug\MyApplication.exe'
I did send publishing diagnostic to the Output and get this :
Task "GenerateApplicationManifest" (TaskId:158)
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(2580,9): error MSB3113: Could not find file 'obj\x86\Debug\MyApplication.exe'.
Done executing task "GenerateApplicationManifest" -- FAILED. (TaskId:158)
Done building target "GenerateApplicationManifest" in project "MyApplication.csproj" -- FAILED.: (TargetId:194)
Can someone list all things I have to check to get this issue fixed ?

I just ran into the problem today. In my particular case, it was caused by this Microsoft Windows Update.
I uninstalled that update and publish began working as it always had. This is only a temporary work around and means you should probably regenerate your keys/certificates.

Right click on you Project
Click Publish
Go to Settings Tab
Click File Publish Options
Check All the options in the tab (As seen in attached image)

Related

How to fix "unknown project ID (no ID found ) (Dispatcher API Error: 9)[CR][LF]" error?

I am working on Captiva designer and my flow includes recognition project for Classification.
It was working all fine earlier, however I made one change recently. Just after that, the mentioned error started to show up. I have tried to keep the backup project back in location(which was working fine earlier), however now that also showing the same error now.
unknown project ID (no ID found ) (Dispatcher API Error: 9)[CR][LF]
How to get it fixed?
You need to compile the recognition project after you made the changes.
Without compiling, it might show you as saved, but when you deploy the flow, it might cause the project ID issue. Usually this issue happens when you copy the recognition profile from other environment. So once you copy or modify the existing recognition project, you should go to recognition -> open your project -> compile it and then map it with the flow, using classification setup.

SQL Server Database Project dbml file is always modified [duplicate]

I'm running into a small but weird annoyance that seems to be happening to other people, too (for example, check out the revision history of SEDE). I have a SQL Server 2008 database project in Visual Studio 2010 that works properly. When I go to commit/checkin to source control, I'm told that my DB project's .dbmdl file has changed, even when I've made no changes to the project!
I'm not sure if the changes are triggered by building my solution (which also includes an ASP.NET MVC application and a unit test project) or by simply opening the DB project, but this is getting kind of annoying and is creating clutter in source control.
Is it possible to stop these changes from occurring, or get rid of the .dbmdl file whatsoever?
If you delete the .dbml file, it is rebuilt without errors or warnings, so I think it's just a cache file for references, intellisense, etc. I'm going to exclude it from source control.
I believe Visual Studio serializes the dbmdl file every time the project is opened. The only possible work around would be to keep the project open.
See related question here. The .dbmdl file is unique per user (and some kind of cache, as said above) and so the right solution is indeed to exclude it from source control.

Jdeveloper Migration from 10g to 12C

I am using Jdeveloper10g in my current project. Now I want to migrate it to Jdeveloper12c.
so I download the Jdeveloper12c and open the Jdeveloper10g application into it.
Before open the application it run the migration tools. which migrate application successfully.
But actual problem arise after migration.
Project Structure :
Service Layer with EJB2.0 (Migrated and deployed successfully)
View
ADF_Module (BC )
In this architecture Service Layer component which has been written in EJB2.0 successfully compiled and deployed with any error.
But View and ADF_module failed for compilation.
In my first R&D I found View and ADF_Module both are dependent to each other . Both are using each other Api.
So when compiler go to compile the view.jpr it does not find ADF_Module class and shows error.
I do not know I to fix this error. Second this structure is compiled on Jdev10g.
Can some one help how to remove this cyclic dependencies or fix this complication error.
Thanks
You first need to move 10 to 11
then 11 to 12.
Each migration does changes in the project settings and 10 to 12 directly is not supported.
Your View project should have a dependency on your Model but not the other way around. This can be modified by right click on your project >Project properties > Dependencies > Use the pencil icon to modify the dependencies.

Enable-Migrations causes project failed to build

I have created a sample WPF project, worked fine.
I added a MVVMLight project, made it a default startup project, and ran fine.
Now I added a class library project, and added an ADO.NET data model with "Code First From Database", and selected relevant tables, that gave me a good collection of entity classes.
I thought this way, I can keep my data model seperate from presentation and businesss logic layers, plus add additional target plateforms if needed and take the advantage of SoC.
So far so good.
Now I want to enable Migrations on my data layer only. I fired up Nuget console, selected dataLayer project in the "Default Project" drop down. Issued Enable-Migrations command and very first error I got was
"No connection string named 'dpFinDataModel' could be found in the application config file."
Now I modified Startup project - i.e. Mvvm project's App.Config to add App.Config details from DataLayer project.
Tried to rerun "Enable-Migrations", and following error occured:
PM> Enable-Migrations
The project 'dpFinMvvm' failed to build.
Am I doing something wrong here?
Will this approach work?
Thanks for all your help.
-DP
1) PM> Enable-Migrations would get an error if your project itself contains errors.
Try going through your code such as in debug mode and check if you have any build errors then try.
2) And for your config file error you may have not referenced it properly, try this tutorial to solve your issue.
http://www.asp.net/mvc/overview/getting-started/getting-started-with-ef-using-mvc/creating-a-more-complex-data-model-for-an-asp-net-mvc-application

Why does my DB project's .dbmdl file change even when I make no changes to the project?

I'm running into a small but weird annoyance that seems to be happening to other people, too (for example, check out the revision history of SEDE). I have a SQL Server 2008 database project in Visual Studio 2010 that works properly. When I go to commit/checkin to source control, I'm told that my DB project's .dbmdl file has changed, even when I've made no changes to the project!
I'm not sure if the changes are triggered by building my solution (which also includes an ASP.NET MVC application and a unit test project) or by simply opening the DB project, but this is getting kind of annoying and is creating clutter in source control.
Is it possible to stop these changes from occurring, or get rid of the .dbmdl file whatsoever?
If you delete the .dbml file, it is rebuilt without errors or warnings, so I think it's just a cache file for references, intellisense, etc. I'm going to exclude it from source control.
I believe Visual Studio serializes the dbmdl file every time the project is opened. The only possible work around would be to keep the project open.
See related question here. The .dbmdl file is unique per user (and some kind of cache, as said above) and so the right solution is indeed to exclude it from source control.

Resources