Projects Archives - scmGalaxy https://www.scmgalaxy.com/tutorials/tag/projects/ A Platform for Software Engineers Sat, 27 Feb 2021 09:55:56 +0000 en-US hourly 1 https://wordpress.org/?v=7.1 Extension used in DOTNET and MSBuild Projects https://www.scmgalaxy.com/tutorials/extension-used-in-dotnet-and-msbuild-projects/ https://www.scmgalaxy.com/tutorials/extension-used-in-dotnet-and-msbuild-projects/#respond Sat, 02 Jul 2016 14:08:38 +0000 http://www.scmgalaxy.com/tutorials/2016/07/02/extension-used-in-dotnet-and-msbuild-projects/ .proj A popular convention for generic use. Commonly used by a main build script. Examples: build.proj main.proj company.product.build.proj .targets .targets […]

The post Extension used in DOTNET and MSBuild Projects appeared first on scmGalaxy.

]]> extension-used-in-dotnet-and-msbuild
.proj
A popular convention for generic use. Commonly used by a main build script.
Examples:
build.proj
main.proj
company.product.build.proj
.targets
.targets files are those which is meant to be imported into other files using the Import element. Since these files are strictly re-useable they don’t actually build anything. They typically are missing the properties and item values to actually build anything.
Examples:
Microsoft.Common.targets
Microsoft.CSharp.targets
Microsoft.Data.Entity.targets
.**proj
Language specific convention where **** represents the language short acronym.
Well-known extensions:
.csproj    | C#
.vbproj    | VB.NET
.vcxproj   | Visual C++
.dbproj    | Database project
.fsproj    | F#
.pyproj    | IronPython
.rbproj    | IronRuby
.wixproj   | Windows Installer XML (WiX)
.vdproj    | Visual Studio Deployment Project
.isproj    | InstallShield
.pssproj   | PowerShell
.modelproj | Modeling project
.props
A project property sheet used by Visual C++ projects (.vcxproj).
Examples:
Microsoft.Cl.Common.props
Microsoft.Cpp.CoreWin.props
Microsoft.Cpp.props
Microsoft.Link.Common.props
.tasks
A common include file to be imported by a calling MSBuild project. Contains a list of <UsingTask> elements.
Examples:
Microsoft.Common.Tasks
MSBuild.ExtensionPack.tasks
.settings.targets
(This is a related convention if not strictly-speaking a file extension.)
A common include file to be imported by a calling MSBuild project. Contains “various properties related to shared utilities used during the build and deployment processes as well as any other common settings” (Sayed Ibrahim Hashimi, 2009).
Examples:
EntityFramework.settings.targets
Compiler.settings.targets
Library.Settings.targets

The post Extension used in DOTNET and MSBuild Projects appeared first on scmGalaxy.

]]> https://www.scmgalaxy.com/tutorials/extension-used-in-dotnet-and-msbuild-projects/feed/ 0 Share common projects with two different projects in CVS https://www.scmgalaxy.com/tutorials/share-common-projects-with-two-different-projects-in-cvs/ https://www.scmgalaxy.com/tutorials/share-common-projects-with-two-different-projects-in-cvs/#respond Wed, 07 Jan 2009 06:08:42 +0000 http://www.scmgalaxy.com/tutorials/2009/01/07/share-common-projects-with-two-different-projects-in-cvs/ Share common projects with two different projects in CVS If there are two or more projects in the repository, some of […]

The post Share common projects with two different projects in CVS appeared first on scmGalaxy.

]]> projects-in-cvs

Share common projects with two different projects in CVS If there are two or more projects in the repository, some of the files are common in these two projects and some are different.How to share the files that are same between these projects? How can archive this? How Changes in common files be reflected to both projects. Version of CVS 2.5.03  

Answer: The CVSROOT/modules2 file or the older CVSROOT/modules file can help with this sort of thing:

http://cvsnt.org/manual/html/Administrative-files.html#modulesOrhttp://cvsnt.org/manual/html/modules2.html  

Generally the best CM independent solution is to organise your project source code hierarchy within the CM tool in such a way that ‘common’code is in a project/module/directory of it’s own so it can be checked out and managed independently of other projects, ie:  

/repo/proja 

/repo/projb 

/repo/common 

Then you define a module where ‘projecta’ = ‘proja’+’common’ so when a person does ‘cvs co projecta’ they  get: 

/projecta/proja 

/projecta/common 

If your server is running on Linux then you can ‘cheat’ by simply symbolically linking the RCS file into two directories (though this may cause locking conflicts if the files are very busy).   

Thanks to:Arthur Barrett 

The post Share common projects with two different projects in CVS appeared first on scmGalaxy.

]]> https://www.scmgalaxy.com/tutorials/share-common-projects-with-two-different-projects-in-cvs/feed/ 0