Barcha *.cshtml fayllari Build Action uchun kontent sifatida o‘rnatilganligiga ishonch hosil qiling

"Yo'q" guruhidagi element .cshtml kengaytmasiga ega bo'lsa, ogohlantirish hosil qiladigan kichik snippet bilan .csproj ni kengaytirishingiz mumkin. Snippet quyidagicha bo'ladi:

<Target Name="EnsureContentOnViews" BeforeTargets="BeforeBuild">
  <ItemGroup>
    <Filtered Include="@(None)" Condition="'%(Extension)' == '.cshtml'" />
  </ItemGroup>
  <Warning 
    Condition="'@(Filtered)'!=''"
    Code="CSHTML" 
    File="$(MSBuildProjectDirectory)\%(Filtered.Identity)" 
    Text="View is not set to [BuildAction:Content]"
  />
</Target>

Agar siz boshqa qurish amallarini ko'rsangiz (masalan, EmbeddedResource), ularni Filtrlangan element ta'rifiga qo'shishingiz mumkin.

Agar siz yanada rivojlangan aniqlashni istasangiz, ushbu Xpath //ItemGroup/*[not(self::Content)]/@Include ga mos keladigan har qanday element uchun loyiha fayllarini tahlil qilishingiz kerak.

<Target Name="EnsureContentOnViewsXML" BeforeTargets="BeforeBuild">
  <XmlPeek XmlInputPath="$(MSBuildProjectFile)" Namespaces="&lt;Namespace Prefix='msb' Uri='schemas.microsoft.com/developer/msbuild/2003'/&gt;"; Query="/msb:Project/msb:ItemGroup/*[not(self::msb:EmbeddedResource)]/@Include">
    <Output TaskParameter="Result" ItemName="AllItems" />
  </XmlPeek>

  <!-- MsBuild uses XPath 1.0 which doesn't have the 'ends-with' or 'matches' function. -->
  <ItemGroup>
    <Filtered Include="@(AllItems)" Condition="'%(Extension)' == '.cshtml'" />
  </ItemGroup>

  <Warning 
    Code="CSHTML" 
    File="$(MSBuildProjectDirectory)\%(Filtered.Identity)" 
    Text="View is not set to [BuildAction:Content]"
    Condition="'@(Filtered)'!=''"
  />
</Target>

<Warning ...> o'rniga <Error ...> dan ham foydalanishingiz mumkin

Loyiha faylingizga ushbu parchalardan birini qoʻlda kiritishingiz kerak boʻladi:

Meni boshlaganingiz uchun jessehouwing sizga rahmat! Menga sizning yechimingiz yoqdi va unga ovoz berdim. Men u bilan bir oz muammoga duch keldim va quyidagi bilan yakunlandim:

<Target Name="EnsureContentOnViews" BeforeTargets="BeforeBuild">
    <ItemGroup>
      <Filtered Include="@(None)" Condition="'%(Extension)' == '.cshtml'" />
    </ItemGroup>
    <Error Condition="'@(Filtered)'!=''" Code="CSHTML" File="%(Filtered.Filename)" Text="Not set to [BuildAction:Content]: Identity: %(Filtered.Identity)" />
</Target>

csproj faylida mening </Project> tegim oldida.

Albatta, @jessehouwing men uchun ishlagan! Shunday qilib, bu tuzatish mening .csproj faylimda yaxshi saqlanib qoladi :).... Faqat, men ikki marta tekshirib ko‘rdim va go‘yo o‘sha yoqimli parcha boshqa dasturchining birlashishi yoki biror narsa tufayli so‘nggi oyda biror joyda g‘oyib bo‘lganga o‘xshaydi.. (haqiqiy voqea). )

NPM alternativi

Baribir, men yaratgan check-vs-includes NPM modulini eslatib o‘tmoqchiman. Buning uchun. Bu, ayniqsa, Tugun o'rnatilgan ishlab chiquvchilar uchun qulaydir (agar o'rnatmasangiz, ehtimol kerak :) ).

Men har bir tuzilishda emas, har bir joylashtirishdan oldin tekshirishni qo'lda bajaraman. Ammo birlashma tufayli .csproj faylingizdan yo'qolib qolish ehtimoli kamroq (sezmasdan).

Biroq, ushbu NPM paketidan foydalanishning asosiy afzalligi shundaki, Build Action NONE-ni tekshirishdan tashqari, u sizning loyihangizga umuman kiritilmagan fayllarni ham tekshiradi. Chunki bu Visual Studio'ning Web Deploy dasturidan foydalanganda (nozik, ammo yomon) xatolarga olib kelishi mumkin. Quyidagi hollarda etishmayotgan qo'shimchalar bo'lishi mumkin: 1) jamoangizda 1 ta VS bo'lmagan dasturchi bo'lsa yoki 2) .csproj faylining birlashishi (ko'pincha birlashma bilan bog'liq muammolar mavjud) tufayli.

Ko'rsatmalar uchun NPM sahifasini tekshiring. Ammo quyida siz Node va Gulp dan foydalanasiz deb taxmin qilinadigan oddiy misol:

Oddiy misol

1. #P6#

   #P7#

2. gulpfile.js-ga vazifa qo'shing:

     var checkVSIncludes = require('check-vs-includes');

     ...

     gulp.task('checkVSIncludes', function() {
        checkVSIncludes(['/Views/**/*.cshtml', '/app/**/*.js']);
     });

3. Tekshirishni loyihangiz papkasida bajaring (masalan, .csproj faylingiz qaerda)

   #P9#

Men maxsus qurish vazifasini amalga oshirishni taklif qilaman. Uni msbuild/tfs skriptingizda prebuild-da chaqiring. Maxsus qurish vazifasi .scproj faylini tekshirishi kerak, agar hech qanday qurish amali boʻlmagan cshtml qoʻshish fayli mavjud boʻlsa. Shunday qilib, nolga teng bo'lmagan int qiymatini qaytarib, chiqing.