Search Results

Search found 186 results on 8 pages for 'csproj'.

Page 5/8 | < Previous Page | 1 2 3 4 5 6 7 8  | Next Page >

• Visual Studio 2010 web.config transformations (TransformWebConfig target)

  - by Jeff D

  I am trying to write unit tests for my transformations, so I am running: msbuild migrated-project.csproj /p:Configuration=Release /T:TransformWebConfig. This works for a new project I create in VS2010, but doesn't in this project. I'm assuming it's because it was originally a 2008 project. I know this is supposed to run in a webplatformbuild whatever, but what I'm trying to do, is just run the transform, so I can grab the transformed web.config, and run some unit tests to make sure the right values exist. I don't see TransformWebConfig referenced as a target in either project, so I'm not sure what I'm looking for.

  Read the article

• .net framework sdk version(csc.exe) using vcbuild.exe on the command line.

  - by r9r9r9

  I create a c# class library project named: testVcBuild, then use vcbuild.exe to build the project in the command line like: C:\Program Files\Microsoft Visual Studio 9.0\VC\vcpackages>vcbuild testVcBuild.csproj "Debug|Win32" the out put shows: Microsoft (R) Visual C++ Project Builder - Command Line Version 9.00.21022 Copyright (C) Microsoft Corporation. All rights reserved. Microsoft (R) Build Engine Version 2.0.50727.4927 [Microsoft .NET Framework, Version 2.0.50727.4927] Copyright (C) Microsoft Corporation 2005. All rights reserved. I found that the vcbuild.exe always call the "C:\Windows\Microsoft.NET\Framework\v2.0.50727\Csc.exe /noconfig .." the problem is how can I change the Framework version to v3.5? I found my project works fine with the v3.5 but it's broken in the v2.0.50727. I try to use msbuild.exe instead of vcbuild.exe, everything goes well, I just don't understand how can I make it with the vcbuild.exe? win7+vs2005+vs2008 installed.

  Read the article

• Where is PostSharp.Public 1.5 DLL ?

  - by jfneis

  Fellows, I'm going crazy with looks like a really stupid problem. I'm trying to build a simple example using PostSharp as a log AOP utility. I've not installed PostSharp, and I don't want to, I want to reference the necessaries DLLs, change my .csproj and see everything working. Change the project and add references was kind of easy, byt just after adding the LogAttribute to a method I got two errors: Error 1 'Log4PostSharp.LogAttribute' is not an attribute class C:\Dev\LogWithPostsharp\LogWithPostsharpCmd\Program.cs 17 10 LogWithPostsharpCmd Error 2 The type 'PostSharp.Extensibility.MulticastAttribute' is defined in an assembly that is not referenced. You must add a reference to assembly 'PostSharp.Public, Version=1.5.0.0, Culture=neutral, PublicKeyToken=b13fd38b8f9c99d7'. C:\Dev\LogWithPostsharp\LogWithPostsharpCmd\Program.cs 18 22 LogWithPostsharpCmd The first error really looks like consequence of the second, but here is the deal: the PostSharp.Public.* simply doesn't exist in the downloaded .zip. Is there something that I'm not getting? Thank you in advance. Filipe

  Read the article

• How to get VS2010 Web.config Transformations working from NAnt?

  - by jmcd

  In my Nant file I've got (paths shortened): <echo message="#### TARGET - compile ####"/> <echo message=""/> <echo message="Build Directory is ${build.dir}" /> <exec program="${framework}\msbuild.exe" commandline="..\src\Solution.sln /m /t:Clean /p:Configuration=Release" /> <exec program="${framework}\msbuild.exe" commandline="..\src\Solution.sln /m /t:Rebuild /p:Configuration=Release" /> <exec program="${framework}\msbuild.exe" commandline="..\src\Solution.sln /m /t:TransformWebConfig /p:Configuration=Release" /> Which results in: Build FAILED. "C:\..\src\Solution.sln" (TransformWebConfig target) (1) -> C:\..\src\Solution.sln.metaproj : error MSB4057: The target "TransformWebConfig" does not exist in the project. [C:\..\src\Solution.sln] 0 Warning(s) 1 Error(s)Time Elapsed 00:00:00.05 The solution and associated projects are all VS2010 and the Web Application even has the correct reference in the .csproj: <Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets" /> Shouldn't this just work?

  Read the article

• Which c# project files should I version control?

  - by DTown

  I have a project I'm looking to manually manage via perforce version control as I only have the Express edition. What I'm looking for is which files should be excluded in the version control as locking many of the files can result in a problem for visual studio compiling and debugging. What I have, so far, included. .cs files (except properties folder) .resx files .csproj files Excluded bin folder obj folder Properties folder .user file Let me know if there is something more that should be included that I have excluded or if there is a better way to do this.

  Read the article

• MSBuild Override Project Reference to resolve to Precompiled Assembly

  - by Ryu

  Situation I have about 400 csproj files using project references. About 3 of those a separate team wants to fork and incorporate into a standalone app. I branched the 3 projects of interest, and because the separate team uses a diff SVN repo I used svn externals to pull in these projects into the folder of the standalone app. Obviously since this team uses a different folder structure the project references no longer resolve. Attempted Solution I figured setting the msbuild properties ReferencePath and AdditionalLibPaths to point to a directory with all the precompiled dependencies would allow the project references a fallback point and resolve correctly. However that doesn't appear to be the case. Question Does anybody know a way to have a failed projectreference look up resolve to the precompiled dll? Perhaps point me to an automated tool to convert projectreferences to dll references? Or is there a better way to solve this problem? Thanks

  Read the article

• Copy task in Visual Studio 2008

  - by Maurizio Reginelli

  This is a question related to a previous question I posted (see here). I need to configure a .csproj file to copy some files from a directory to another one (let me call them SOURCE and DESTINATION). I also need to change the SOURCE path depending from the configuration I'm using. For example, if I compile my project in Debug mode, the SOURCE path must contain a subfolder called Debug. I tried the solution proposed by Schmitt in the previous post, using $(ConfigurationName) to set the dynamic directory into the SOURCE path. When I opened the solution containing that project, a list of links to the source files appeared in the main tree of the project and they were correctly related to the Debug mode. But when I changed to the Release mode, I saw that the path of the linked source files were set again to the Debug version. Is there a way to specify a parameter in the Include attribute of the SourceFiles element? Thank you.

  Read the article

• How do I execute a command on a successful build on TFS2010?

  - by Simon_Weaver

  I've got TFS2010 up and running and building a webdeploy deployment package. Into my directory: C:\TFS-BUILDS\Example Build\Example Build_20100414.44\_PublishedWebsites I get the following two directories: WebsiteName WebsiteName_Package All I want to do is run the following command on a successful build - to deploy the site: WebsiteName_Package\WebsiteName.deploy /Y How can I customize the build process template to actually run that package? Under TFS 2010 you have to use the process templates (no more TFSBuild.csproj stuff). I've tried duplicating the DefaultProcessTemplate.xaml file, but it basically kills my Visual Studio when I open it. How can I edit the .xaml by hand to run this simple command on a successful build

  Read the article

• Preventing referenced assembly PDB and XML files copied to output

  - by Jason Morse

  I have a Visual Studio 2008 C#/.NET 3.5 project with a post build task to ZIP the contents. However I'm finding that I'm also getting the referenced assemblies' .pdb (debug) and .xml (documentation) files in my output directory (and ZIP). For example, if MyProject.csproj references YourAssembly.dll and there are YourAssembly.xml and YourAssembly.pdb files in the same directory as the DLL they will show up in my output directory (and ZIP). I can exclude *.pdb when ZIP'ing but I cannot blanket exclude the *.xml files as I have deployment files with the same extension. Is there a way to prevent the project from copying referenced assembly PDB and XML files?

  Read the article

• Why does MSBuild fail from the command line where VS2008 succeeds?

  - by sundeep

  I have an ASP.NET solution that builds just fine from within VS2008. However , it fails when i do this : MSBUILD.exe c:\path-to-sln It fails with a CS0006 error ("Metadata file 'dll_name' could not be found"). It also fails when I try with a .csproj of a project within the solution. What is VS2008 doing that MSBuild is missing ? It is my understanding that VS knows about inter assembly dependencies that MSBuild cant. Is there any way I can inform MSBuild of these? (I need MSBuild to work from the command line because I am calling it from an MSBuild-Task from within CruiseControl.Net.) Thanks in Advance. :3) (I have looked at http://stackoverflow.com/questions/280559/how-to-get-cmd-line-build-command-for-vs-solution , but still dont get it)

  Read the article

• how to specify the Build Engine Version when using VcBuild.exe on the command line.

  - by r9r9r9

  I create a c# class library project named: testVcBuild, then use vcbuild.exe to build the project in the command line like: C:\Program Files\Microsoft Visual Studio 9.0\VC\vcpackages>vcbuild testVcBuild.csproj "Debug|Win32" the out put shows: Microsoft (R) Visual C++ Project Builder - Command Line Version 9.00.21022 Copyright (C) Microsoft Corporation. All rights reserved. Microsoft (R) Build Engine Version 2.0.50727.4927 [Microsoft .NET Framework, Version 2.0.50727.4927] Copyright (C) Microsoft Corporation 2005. All rights reserved. I found that the vcbuild.exe always call the "C:\Windows\Microsoft.NET\Framework\v2.0.50727\Csc.exe /noconfig .." the problem is how can I change the Framework version to v3.5? I found my project works fine with the v3.5 but it's broken in the v2.0.50727. I try to use msbuild.exe instead of vcbuild.exe, everything goes well, I just don't understand how can I make it with the vcbuild.exe? win7+vs2005+vs2008 installed.

  Read the article

• MSBuild - setting a reference path

  - by Ryan

  I have several assemblies my project is dependant upon. These are stored in the Project's directory under the "Dependencies" folder. So something like this. Solution - Project - Dependancies FunkyAssembly.dll - bin - Debug - Release SomeCode.cs I've referenced FunkyAssembly.dll using Browse and in project.csproj I see <Reference Include="FunkyAssembly"> <HintPath>Dependancies\FunkyAssembly.dll</HintPath> </Reference> So far so good - except after a release build FunkyAssembly.dll is copied to the Release directory (not a problem in itself) but then future debug builds will reference this copy rather than the copy in Dependencies. You can see this if you at Path in the reference properties. This means that if Dependencies\FunkyAssembly.dll is updated the build won't pick it up as its referencing the old copy in bin/Release. Any way to FORCE the damn thing to pick up Dependencies\FunkyAssembly.dll rather than HINT?

  Read the article

• Using a single visual studio 2005 solution with multiple source control applications

  - by Bas Bossink

  In my recent SO question I was helped tremendously in using git as a front-end to ClearCase. However actually trying the suggested answer(s) led to further complications. Visual Studio keeps a reference to the used source control provider in both the .sln as well as the .csproj files. I tried resolving this issue by keeping a modified copy of the .sln with the source control provider paragraph removed but this did not help since each project also has some source control provider information. I don't want to keep private copies of all the projects since this would be a maintenance nightmare. Do any of you have suggestions on how to resolve this issue?

  Read the article

• VS2008 Express no longer opens projects after VS2010 express Phone

  - by Alikar

  So I installed the new april release of the VS2010 express for windows phone 7 and now VS2008 express C# no longer opens .csproj files. I'm at a loss as to why this is as I've not changed anything in the files themselves. I'm currently uninstalling windows phone 7 in the hopes that I will be able to open my files again. I have a feeling though I'm going to need to uninstall 2008 as well and the reinstall it to get everything to work. In the future how should I install 2010 express for win 7 phone to prevent it from interfering with 2008 express?

  Read the article

• Getting a Target to run BEFORE anything else runs when building from Visual Studio

  - by damageboy

  Hi, I'm trying to get a one-time costly target to run only when building a certain top-level project (that has many dependencies). I have no problem on getting this working from plain msbuild / command line build. I do this with setting and InitialTargets on the project, or alternatively with < BeforeBuild /. The tricky part is with Visual Studio. When I build the same project from VS. VS runs the dependencies before even invoking my .csproj, so my target (which affects how the other projects are built) doesn't get to run until they have already been built. Is there someway to force VS to run a target before invoking the dependencies? I'm currently working around this, by running the same costly target from my most low-level project (the one that get's always built...) by using: Condition=" $(BuildingInsideVisualStudio) " Any ideas on how to get this done "properly"? Again, I'm looking for a solution that will work FROM VS.

  Read the article

• Platform configuration for projects in VS 2010

  - by Thomas Wanner

  I have a third-party project type in Visual Studio which for some reason only supports the .NET Platform configuration for the build, for all other (standard C#) projects in the solution I only have AnyCPU. Unfortunately, ever since upgrading to VS 2010 it produces following error when built : Error 39 The OutputPath property is not set for project 'ReferencedBusinessProject.csproj'. Please check to make sure that you have specified a valid combination of Configuration and Platform for this project. Configuration='Debug' Platform='.NET'. This error may also appear if some other project is trying to follow a project-to-project reference to this project, this project has been unloaded or is not included in the solution, and the referencing project does not build using the same or an equivalent Configuration or Platform. C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets 483 10 CustomTypeProject It's pretty much descriptive in what is missing but I haven't found any way to fix it so far. Do you have any idea how this can be resolved or what can be the problem ?

  Read the article

• Opening a Silverlight project causes APPCRASH is Visual Studio 2008

  - by Ed Woodcock

  Hi guys I've got to add a Silverlight project to a solution for a deployment procedure (it's a pre-build dependency for the main project). I've installed Silverlight tools v3, silverlight itself and the silverlight sdk 3, and am using Visual Studio 2008 with ReSharper and the DevArt oracle database tools. Every time I go to open the relevant silverlight .csproj file VS crashes with the following error message: Problem Event Name: APPCRASH Application Name: devenv.exe Application Version: 9.0.30729.1 Application Timestamp: 488f2b50 Fault Module Name: StackHash_20af Fault Module Version: 6.0.6001.18000 Fault Module Timestamp: 4791a7a6 Exception Code: c0000374 Exception Offset: 000b015d This also happens if I try to create a new silverlight project from scratch. Does anyone have any suggestions?

  Read the article

• VS2008: Disable asking whether to reload files changed outside the IDE

  - by SealedSun

  Hi, I have a Visual Studio 2008 project where some code files are generated with each build (a parser, integrated via MSBuild aka editing the *.csproj file). VS does not know about the generated nature of these files (i.e. they are not the result of a "Custom Tool). So they "change" with every build, naturally. And VS2008 asks me after every build if I would like to reload those files: This file has been modified outside the source Do you want to reload it? That would be ok if I had one of those files opened and in front of me, but I get these modal dialogs even with none of the code files opened. So my question is: Is there a way to disable this dialog, per project, per solution or globally? Thanks!

  Read the article

• Conditionally embed ASP.NET MVC2 Views as resources during build in Visual Studio 2010

  - by jslatts

  I have a ASP.NET MVC2 project in VS2010 that can be deployed in two modes: standalone or plugin. In standalone mode, the views should live outside the compiled assembly as .aspx files (the default setup). In plugin mode, the views are switched (currently by hand) to embedded resources and the entire assembly is dropped into a host project folder. Currently, this requires the developer to go through each view and switch it from Build Action: "Content" to "Embedded Resource" and vice versa. I would like to create a new solution configuration to automatically grab all .aspx files and build them as resources. This SO post seems like the solution, but I would prefer not to have to edit the .csproj every single time I add a new view to the project. Is there a way to use a wild cards or some other batch/global conditionally statement to change resources from content to embedded?

  Read the article

• Visual Studio creating bin/ folder in wrong location.

  - by Joviee

  In Visual Studio 2008, I have a solution with a number of projects. Each project has the same build output path of "..\bin\Debug\" for debug, and "..\bin\Release\" for release. So the directory structure looks like this: solution\ bin\ project1\ project2\ project3\ This all works fine, all the assemblies go to the correct location when I build the project, etc. Howevever, when I first open the solution in Visual Studio, an empty bin folder is created one level up from where it should. So I am getting: bin\ solution\ bin\ project1\ project2\ project3\ This folder is only created when I first open the solution. Never when I build. I have looked through the .sln and every .csproj file, and I cannot work out why this folder is being created. So, my questions are: a) Why is this bin folder being created? b) How do I stop Visual Studio from creating this bin folder?

  Read the article

• Visual Studio Macro: How to perform "File -> Save All" programatically

  - by Sean B

  I am looking for the equivalent of running "File - Save All" before certain Rake macros. What I have so far is: Private Sub Pre_Rake() Dim i As Integer DTE.Documents.SaveAll() For i = 1 To DTE.Solution.Projects.Count If Not DTE.Solution.Projects.Item(i).Saved Then DTE.Solution.Projects.Item(i).Save() End If Next End Sub DTE.Documents.SaveAll works fine, but the for loop does not save the project files as I would expect. If I make a copy of a file in the solution explorer, that file is not included in the project file (.CSPROJ) after Pre_Rake() runs. I would still have to press CTRL-SHIFT-S or File - Save All. So, how to Save All with a Visual Studio Macro?

  Read the article

• $(MSBuildStartupDirectory) in Visual Studio points to different places on different machines

  - by skolima

  In a large solution, I'm integrating Gendarme into Visual Studio 2008 compilation process. I am using GendarmeMsBuild task along with a .targets file to add a AfterBuild target to every project in the solution. I am looking for a way to import this file into .csproj files in a way that wouldn't require me to change the include path (the projects have different nesting levels). Apart from using NuGet SolutionDir variable, best way to solve this seemed to be to use $(MSBuildStartupDirectory). However, as it turns out, on some machines, using the same version of VS 2008 (as same updates installed, as far as I was able to check) this resolves to the solution directory, and on others to c:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE. How can I either get this to always resolve to the solution folder or obtain the base folder in another consistent way?

  Read the article

• MonoDevelop seems to hang (not unresponsive) when building csprojs

  - by Michael Shimmins

  Building a solution from Visual Studio in mono develop seems to have some issues. I'm hoping someone else has experienced this and has some suggestions. The actual dcms process goes pretty quickly, but in between projects it hangs after printing: Building: XXX.YYY.ZZZ (Debug) After a few minutes (been 10 so far on this current run), it jumps to: Performing main compilation... /Library/Frameworks/Mono.framework/Versions/2.10.1/bin/dmcs /noconfig "/... Build complete -- 0 errors, 0 warnings Building: XXX.YYY.ZZZ (Debug) Then hangs again for another few minutes. This is a sln file with 29 csproj projects in it that was originally created in Visual Studio 2010. I'm wondering if there is a better way to set this up - potentially a native MD file format?

  Read the article

• Working effectively unit tests / Anyone tried the in-assembly approach?

  - by CodingCrapper

  I'm trying to re-introduce unit testing into my team as our current coverage is very poor. Our system is quite large 40+ projects/assemblies. We current use a project named [SystemName].Test.csproj were all the test code is dumped and organised to represent the namespaces using folders. This approach is not very scalable and makes it difficult to find tests. I've been thinking about added a Tests folder to each project, this would put the unit tests "in the developers face" and make them easy to find. The downside is the Production release code would contain references to nunit, nmocks as well as the test code and test data.... Has anyone tried this approach? How is everyone else working with unit tests on large projects? Having a Tests project per "real" project/assembly would introduce too many new projs. Thanks in advance

  Read the article

• Working effectively with unit tests / Anyone tried the in-assembly approach?

  - by CodingCrapper

  I'm trying to re-introduce unit testing into my team as our current coverage is very poor. Our system is quite large 40+ projects/assemblies. We current use a project named [SystemName].Test.csproj were all the test code is dumped and organised to represent the namespaces using folders. This approach is not very scalable and makes it difficult to find tests. I've been thinking about added a Tests folder to each project, this would put the unit tests "in the developers face" and make them easy to find. The downside is the Production release code would contain references to nunit, nmocks as well as the test code and test data.... Has anyone tried this approach? How is everyone else working with unit tests on large projects? Having a Tests project per "real" project/assembly would introduce too many new projs. Thanks in advance

  Read the article

< Previous Page | 1 2 3 4 5 6 7 8  | Next Page >