I can't believe this. I tried to add splash screen by following the guidelines from the MSDN but my WPF application project broke because of this. Now I cannot debug & run the application anymore.
The only message that I get is:
Project file cannot specify more than one Splash Screen element
There is no location where it happens. When I take a look at the output window, it looks like this..
------ Build started: Project: MPCS Line Off, Configuration: Debug x86 ------
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.WinFX.targets(269,9): error MC1004: Project file cannot specify more than one SplashScreen element.
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.WinFX.targets(269,9): error BG1003: The project file contains a property value that is not valid.
I have searched high and low, but no luck. FYI this is in VS2010.
There are more than one file with "Build Action = SplashScreen"
Related
I'm following this tutorial for setting up an app.config on a Xamarin app.
The Tutorial
one of the last steps is:
Add this PCL app.config file as a linked file on all your platform projects. For android, make sure to set the build action to ‘AndroidAsset’, for UWP set the build action to ‘Content’
Access your setting:
I have no idea what they are taking about, how in Vs2017 do I add a file as a linked file to the sub-os projects?
I'm sure this is stupid simple, but I'm totally missing it. thanks.
I figured it out
Right click on Project, add existing select teh file, on the add dialog the add button has a dropdown, change it to add link.
Pretty much every time I go to build the setup project in my solution, I get the following error: "Invalid or unspecified target for shortcut". MSDN provides the following useless help. When I go to the dialog to (re-)select the target for the shortcut:
My primary output (for my main application) is not present, even though it is definitely listed in the File System view:
The setup project was deleted and completely re-created, and checked in. When it was checked back out, I got the exact same error.
I assume that whatever reason is causing the item to not show up in the "select target" dialog, is the same reason that the build is failing in the first place. What gives?
I just solved this by changing my build mode from Debug to Release.
Primary Output for ... (Release x86) - It is looking for a release build of x86.
If you look at your Errors List you should see the error listed. Right click on it and choose the Properties Window.
Find the "Target" property and simply set it to the correct value.
This goes for the Icon problem as well.
In my case, I was building and packaging a Net.Core project using a Publish Profile.
The publish was failing with no visible error during the Msi build.
I ran the publish profile manually and saw the error that I had 2 copies of appsettings.json being installed at the same location.
I excluded one of the files and both the Publish and Package completed successfully and the shortcuts became valid again.
I have to create around 200 WP7 apps that are very similar. They differ only in the content, icons and name. So manually create them isn't a good idea so let's I've written a little tool, which does the following:
Copy the created template project
Copy the content files from a source directory to the copied template.
Change the app name, tile name and app id in the WMAppManifest.xml
Add the copied content files in the .csproj-file.
This works and the generated project opens error-free in Visual Studio 2010 and compiles without errors. The xap-file can be deployed on device and emulator.
The problems:
If I want to debug the app by pressing F5 in Visual Studio I get "The application could not be launched for debugging. Ensure that the target device screen is unlocked and that application is installed", both for device (which is unlocked and connected with Zune/WPConnect) and the emulator.
If I try to start the app on the emulator it closes immediatle after start. BUT if I start the app on my device it works like a charm. Crazy stuff.
The curious stuff: If I do the things which my little tool does manuelly I can debug the project from Visual Studio.
This only occures with my generated projects. Every other WP7 project (existing or newly created within VS) works and debugs error-free.
I tried to PCs: Win7 x64 with VS2010 Ultimate and an other one Win7 x64/VS2010 Pro and on both maschines I have the problem.
Maybe someone has an idea which causes the problem. Thanks for the help!
Edit: I've seen something new: The AssemblyInfo.cs file is located in the properties folder and correctly included in the csproj-file. But if I try to open the Assembly Information from the project properties all fields are empty and if I try to set them I get an error ("value is not in the expected range" or something like this).
I've got similar problem with some sample programs.
It turned out that I have to set in a Solution properties:
Active config => Debug|Windows Phone
it works for me
If they only differ in content, icons, and name, would it be simpler to make one complete app, copy it 199 times, and then just put the appropriate files into the correct directories?(if you made a tool to make templated projects, i'm sure you could do this with code too)
Plus that way if you ever need to change the program you can just recopy with that code again, but not copy the content, thus updating all of your individual 200 apps.
I'm trying to get the publishing information to show up in my output window when I use the publish wizard from the context menu.
Right now when I go through the publish it only generates two lines:
------ Publish started: Project: NerdDinner, Configuration: Release Any CPU ------
Project "NerdDinner.csproj" (MSDeployPublish target(s)):
Done building project "NerdDinner.csproj".
Does anyone have any idea why it's not showing the details of the publish?
Make sure your in your Options->Project and Solutions->Build and Run->MsBuild Project build output vebosity is at least set to Normal.
This should so you all the files that are being copied etc when you Publish.
I have a project that shares some files between a Mac application and an iPad app. Because of this, I moved the Info.plist and Prefix.pch files for each one into sub folders for Mac and iPad, respectively. I can build the iPad app in Debug configuration without issue, for the simulator and for a device. I get the following messages in the build results:
Process iPad/Fogozine-Info.plist
Precompile iPad/Fogozine_Prefix.pch
with a big green check mark next to both. Everything is fine.
When I build for Release, though, I get the following:
Process Fogozine-Info.plist
The file "Fogozine-Info.plist" couldn't be opened because there is no such file.
Precompile Fogozine_Prefix.pch
Command /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/gcc-4.2 failed with exit code 1
with big red exclamation marks next to them. Is there some build setting I'm missing that's specific to the release build? I can see there's an Info.plist entry in the Build settings, but the end result is the same regardless of if I leave it empty, set it to iPad, or set it to iPad/Fogozine-Info.plist, for all build configurations. I don't see anything related to the Prefix.pch file. This seems like a bug in Xcode. Any help would be greatly appreciated.
I got it. I was looking in the Project's build settings, but I needed to look in the Target's build settings. The two settings I needed to modify were Info.plist File and Prefix Header. When I modified them initially, I must have only modified them for the Debug Build Configuration.