Reputation: 48568
I cloned a repo and in it I got a .psproj
file. I tried opening in Visual Studio 2017 (since notepad++ showed it contained xml much like VS Solutions). In VS also it opened showing internal xml and not as a proj/solution file. Same outcome with VS Code.
So my question is
psproj
file?The file's contents:
<Project ToolsVersion="4.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
<Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
<SchemaVersion>2.0</SchemaVersion>
<ProjectGuid>6CAFC0C6-A428-4d30-A9F9-700E829FEA51</ProjectGuid>
<OutputType>Exe</OutputType>
<RootNamespace>MyApplication</RootNamespace>
<AssemblyName>MyApplication</AssemblyName>
<Name>Bootstrapper</Name>
</PropertyGroup>
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
<DebugSymbols>true</DebugSymbols>
<DebugType>full</DebugType>
<Optimize>false</Optimize>
<OutputPath>bin\Debug\</OutputPath>
<DefineConstants>DEBUG;TRACE</DefineConstants>
<ErrorReport>prompt</ErrorReport>
<WarningLevel>4</WarningLevel>
</PropertyGroup>
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
<DebugType>pdbonly</DebugType>
<Optimize>true</Optimize>
<OutputPath>bin\Release\</OutputPath>
<DefineConstants>TRACE</DefineConstants>
<ErrorReport>prompt</ErrorReport>
<WarningLevel>4</WarningLevel>
</PropertyGroup>
<ItemGroup />
<ItemGroup>
<Compile Include="Script.ps1" />
</ItemGroup>
<Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" />
<Target Name="Build" />
</Project>
Upvotes: 1
Views: 3804
Reputation: 101
It's a powershell project file, but not for Visual Studio, it's for Powershell Studio. The powershell projects for visual studio are .pssproj. It took me forever to figure this out because everyone here was too busy arguing about whether this was a valid question to pro
Upvotes: 10
Reputation: 48568
Ok so going by the comments on questions, it is a powershell project file.
To enable your VS to understand such files, one needs to install respective extension to your VS2015 or VS2017 or VS2013
Nice article on this is here
Upvotes: 5