• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
maya18222

Visual Studio C#

3 posts in this topic

1. How do you set your project to refer to different references based on the build mode? For example, how do I reference

"Libs\someDebugLib.dll" in my debug build

and

"Libs\someReleaseLib.dll" in my release build

2. How come when using .net libraries you dont have to select debug or release versions? ... is the correct one being chosen under the hood? .. if so, how?
0

Share this post


Link to post
Share on other sites
1. In C# you don't. In general when you add a reference you add the debug version. When you are ready to release just include the release version.
2. The only real difference between the two is when in debug the optimizations are disabled. This makes it harder to debug. But you can include either one and they will both work.
0

Share this post


Link to post
Share on other sites
[quote name='TheTroll' timestamp='1345330418' post='4970941']
1. In C# you don't. In general when you add a reference you add the debug version. When you are ready to release just include the release version.
2. The only real difference between the two is when in debug the optimizations are disabled. This makes it harder to debug. But you can include either one and they will both work.
[/quote]

But lets say you're working on a project with lots of references, and if as you say, you just set the debug references, but having to change these to the release versions each time you want to build a release version (which could be quite often, especially if you're keeping track on performance), is a real pain.
0

Share this post


Link to post
Share on other sites
I don't know of any way to do it from the IDE, but you can manually modify the .csproj to change references to conditional references. Basically you find a line that looks like
[code]
<Reference Include="MyAssembly, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
<HintPath>path\to\MyAssembly.dll</HintPath>
</Reference>
[/code]
in your project and change it to something like
[code]
<Reference Include="MyAssembly, processorArchitecture=MSIL"
Condition=" '$(Configuration)'=='Debug' ">
<SpecificVersion>False</SpecificVersion>
<HintPath>path\to\MyDebugAssembly.dll</HintPath>
</Reference>
<Reference Include="MyAssembly, processorArchitecture=MSIL"
Condition=" '$(Configuration)'=='Release' ">
<SpecificVersion>False</SpecificVersion>
<HintPath>path\to\MyReleaseAssembly.dll</HintPath>
</Reference>
[/code]
For the MSBuild condition syntax see [url=http://msdn.microsoft.com/en-us/library/7szfhaft]this[/url].
2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0