• 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.

Archived

This topic is now archived and is closed to further replies.

Origin

Visual Studio .NET Solution File Format

4 posts in this topic

Those of you who have already worked with Visual Studio .NET know that Microsoft changed again their project file formats. While Visual C++ 6.0 needed a workspace file (.dsw) and one or more project files (.dsp), Visual C++ 7.0 .NET needs a solution file (.sln) and one or more VC project files (.vcproj). To be able to convert between the different formats or to create them on the fly, I need to know how the new solution file is structured. Here are the contents of a basic .sln file with one associated project:
Microsoft Visual Studio Solution File, Format Version 7.00
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "Test", "Test.vcproj", "{A4536DB2-D21D-40A9-8CC1-15F295177EBC}"
EndProject
Global
	GlobalSection(SolutionConfiguration) = preSolution
		ConfigName.0 = Debug
		ConfigName.1 = Release
	EndGlobalSection
	GlobalSection(ProjectDependencies) = postSolution
	EndGlobalSection
	GlobalSection(ProjectConfiguration) = postSolution
		{A4536DB2-D21D-40A9-8CC1-15F295177EBC}.Debug.ActiveCfg = Debug|Win32
		{A4536DB2-D21D-40A9-8CC1-15F295177EBC}.Debug.Build.0 = Debug|Win32
		{A4536DB2-D21D-40A9-8CC1-15F295177EBC}.Release.ActiveCfg = Release|Win32
		{A4536DB2-D21D-40A9-8CC1-15F295177EBC}.Release.Build.0 = Release|Win32
	EndGlobalSection
	GlobalSection(ExtensibilityGlobals) = postSolution
	EndGlobalSection
	GlobalSection(ExtensibilityAddIns) = postSolution
	EndGlobalSection
EndGlobal   
The format is pretty straightforward. I'm just wondering what the function of the two GUIDs is. The first GUID (8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942) seems to be the same for all solution files I create with VC.NET. Do you get the same GUID? And do you know what its purpose is? The second GUID (A4536DB2-D21D-40A9-8CC1-15F295177EBC in this case) varies from solution to solution (or rather project to project). Is this just a random GUID to uniquely identify a project? When creating .sln files on the fly, may I use CoCreateGUID() or a similar function to create that GUID? By the way: If anybody knows of the exact file format specifications, just drop a link to it and that'd be fine. [edited by - Origin on July 18, 2002 8:36:35 AM]
0

Share this post


Link to post
Share on other sites
Rather than parsing this file yourself, I think you should have a look at the APIs for automating visual studio. I haven''t used these myself in VS.Net so I can''t tell for sure they have everyting you need, but I''d be surprised if you couldn''t use anything from them. See http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsintro7/html/vxoriExtensibilityReference.asp and also http://msdn.microsoft.com/msdnmag/issues/02/01/Bugslayer/Bugslayer0201.asp

I don''t know the answer to your questions, but I guess the file format is unsupported (guess you already figured that out, huh?). The first GUID seem to be the version of Visual Studio used when creating the solution. The second GUID seem to be exactly what you say.

OT: Don''t you find it a little bit odd that they don''t use an XML-based format?
0

Share this post


Link to post
Share on other sites
developer,

thanks a lot for your hints. Yeah, the file format seems to be
unsupported, that''s not surprising though. That they don''t use
XML for their new workspace file format is really odd because
they use XML for everything else now. The new project files are
also based on XML.

I browsed through the links you posted and will have a detailed
look at them later. I guess that they might help me with my
task but I''m wondering if it wouldn''t actually be easier to
parse the files on my own...

As for the GUIDs, is the first one always the same for VC++ 7.0,
i.e. does the same GUID occur in your solution files, too?
0

Share this post


Link to post
Share on other sites
All of my solution files share the same ''first'' GUID, but it''s different from yours. I''m guessing it''s specific to each installation of VS.NET.
0

Share this post


Link to post
Share on other sites
Thanks.

I already expected that. It''s probably part of Micro$oft''s
new "transparent user" policy... Maybe the GUID is the encoded
serial number or something like that. I''ll try and see if a
random GUID works as well. If it does, I don''t see a problem
there.
0

Share this post


Link to post
Share on other sites