I have two Frameworks to be added to the project, one for debug and the other for release
is there a way to add them in Embedded content for each build configuration without doing this manually?
Related
I have an app for ios and android written in Xamarin which I am trying to build with Bitrise.
In the platform project I have 10 build configurations for different releases of the app. In the two submodule projects I have simply a debug & release configuration (and debug|iPhone & simulator on the ios project) - these projects don't need to know about which release of the app is going out - the build config's are for resources and manifest/plist details.
In the solution I use configurations mappings to specify what build config should be used for the submodule projects, i.e.
Solution Configuration : Release_a_particular_version
Platform project maps to : Release_a_particular_version
Core project maps to : Release
Submodule Library maps to : Release
This builds fine in Xamarin Studio or Visual Studio but when building in Bitrise gets an error, project configuration not found.
If I create configurations in both submodules with the same name as the solution_configuration everything builds well.
I imagine there's an msbuild switch to turn configuration mapping on? If there is, how would I apply that to the bitrise build step?
Or some alternative?
Without your Bitrise configuration and the failed build log, it is hard to answer this question.
To help you, we would need to take a look on your configuration and on the failed build log.
You can reach out our support team on Bitrise on-site-chat (on every Bitrise page you can find a message icon in the lower right corner where you can send us a message).
Can I make a build configuration in CLion that builds both Debug and Release verions?
By default "Build All" only builds Debug. I can change it to build Release instead, but that's not what I want. I want a single configuration that builds both Debug and Release.
The problem is that otherwise, my Debug and Release versions may get out of sync, which can lead to confusions later on.
Try using Before Launch -> Run Another Configuration to add your other Debug/Release configuration.
In Netbeans 8.1 I'm trying to debug some files, but Netbeans won't let me add them as debugging sources. To add the sources, I clicked Window > Debugging > Sources. Then in the Sources tab, I right-clicked and selected Add Source Root. Then I selected the source folder and clicked add, but nothing was added.
When I've run into this problem, it is usually because Netbeans cannot see the sources I'm trying to debug. If I'm trying to debug a project's sources, occasionally Netbeans won't allow me to add those sources. This is usually because Netbeans cannot see the sources, so I recommend the following steps:
Open the project in Netbeans by clicking File > Open Project.
Look at the sources of the project and ensure that the file you are trying to debug is visible there.
If the file is not visible then Netbeans cannot see the sources so add the source folder to the project or reconfigure your project so that the sources are shown in the project in Netbeans.
If the sources have not already been added as debugging source, add them using the steps you mentioned.
We are experimenting with nuget for our visual studio projects. However, we only (or at least mainly) use nuget for our own external references, and we store them in a local repository (network share). What I would like to know is how to handle the whole debug/release situation.
Concrete (simplified) situation:
We have a main project that has references to two shared components that we developed ourselves. These shared components are also used in other products of our company
When we build the main project (azure pipelines), we build the debug and release versions of the project. However, we can only specify a single nuget package for each external reference.
What we want to accomplish to to use the debug version of the shared components during the debug build, and the release version during the release build. However, these are (as far as I know) actually different packages.
What is the way of tackeling this issue? Is there, for instance, a way to include both the release and debug versions in a single nuget package? Is it possible to have to different nuget configurations for different build configuration settings?
I've found Best practices with Nuget: Debug or Release?, however this topic doesn't really address my issue. This thread is more a discussion about whether to publish debug or release versions to a remote server. We want to publish both and use both in a private repository. We have no intention of sharing our libraries with the rest of the world.
A NuGet package will normally hold just a single set of assemblies for a particular target framework. It is not really designed to ship a debug and release version since you are publishing the NuGet package to be consumed by other users. Normally you do not publish a debug and a separate release version of your application to end users.
You may be able to workaround this by using a custom MSBuild .targets file in the NuGet package that has its own references and configuration information. You can use this .targets file as an extension to your project. It will be imported so you can define the references as you need based on the configurations defined in your project. It is not ideal but it should work.
Visual Studio 2013.
I have a solution that builds under Release and Debug configurations (with all project configurations set appropriately to Release and Debug). I have added a custom configuration called "Staging" and set only the web app startup project to this configuration (all other dependencies are still set to Debug).
When I try to build the web app I get...
SGEN : error : Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
If I switch the web app project configuration back to Debug it works. I have removed the Staging config from the web app and recreated it based on the Debug config but still have the error.
I've been stuck on this for 3 hours so any help is much appreciated.
Just to clarify, the Staging configuration is exactly the same as the Debug configuration except the startup web app is using a Staging config. This config has been deleted and recreated based upon the Debug config.
I found an answer here...
http://hashtagfail.com/post/5255977780/sgen-loaderexceptions-error
Debugging SGEN didn't reveal anything, but I disabled xml serialization since it appears it's only useful for Release builds.