Let's use a publish profile on that Azure Pipeline on TFS !

-
So we have TFS at work and i have been planning to create a build for a vendor web app which we used the DI the vendor implemented to inject our own custom modules/apps.
i managed previously to create a customized publish profile to produce a web package that contain both the vendor DLLs and our own.


<!--Cutome entry to include custom DLLs-->
  <target name="CollectHelpers">
    <itemgroup>
      <_customfiles include="$(MSBuildProjectDirectory)\bin\Custom*.dll">
      <filesforpackagingfromproject include="%(_CustomFiles.Identity)">
        <destinationrelativepath>bin\%(RecursiveDir)%(Filename)%(Extension)</DestinationRelativePath>
</filesforpackagingfromproject>
    </_customfiles>
  </target>
  <target name="CollectCustomizations">
    <itemgroup>
      <_customfiles include="$(MSBuildProjectDirectory)\bin\*Custom*.dll">
      <filesforpackagingfromproject include="%(_CustomFiles.Identity)">
        <destinationrelativepath>bin\%(RecursiveDir)%(Filename)%(Extension</DestinationRelativePath>
      </filesforpackagingfromproject>
    </_customfiles>
  </target>
  <propertygroup>
    <copyallfilestosinglefolderforpackagedependson>
      CollectHelpers;
      CollectCustomizations;
      $(CopyAllFilesToSingleFolderForPackageDependsOn);
    </copyallfilestosinglefolderforpackagedependson>

    <copyallfilestosinglefolderformsdeploydependson>
      CollectHelpers;
      CollectCustomizations;
      $(CopyAllFilesToSingleFolderForMsdeployDependsOn);
    </copyallfilestosinglefolderformsdeploydependson>
  </propertygroup>
  <!--End of Custom entry-->


finally i did manage to use that custom publish profile on my build pipeline adding this "/p:PublishProfile=$(BuildConfiguration)" to my "Build Solution" step. i used "$(BuildConfiguration)" because i named my publish profiles same name as my build configurations.

Popular posts from this blog

how to copy NuGet packages from one project to another

-
You probably faced that problem at least once, here you are working on your modules trying to build a new model for your solution, create a new dll project and ... here it comes, NuGet packages, you need to have manually install all these NuGet packages that you know form the base of needed libraries for your new module or plug-in, and you need to get every package plus the versions right. If you are like me this would be a soul crushing task to do, so in order for me to be more "efficient" i searched for a way to copy that to the new project, at first i thought well that is easy, just copy "package.json" file, right? , wrong see for some reason this didn't work for me, i was not able to simply do this and restore packages, things went crazy and it seems it's like taking forever! so i have to come up with something even more "efficient" so here you go, hope this save you sometime and but smile on your face just execute below on Visual Studio
Read more

How to load a DLL and runtime, invoke a method by name, get result object and use it as a parameter on another unkown DLL .NET Core

-
That post title took me a while to come up with, but my idea is pretty simple, what id you need sort of a bootstrap that don't reference DLLs, still be able to manage a simple operation of of invoking methods and pass results to the next DLL on the list. C# and .NET Core as a strong type based doesn't really have obvious ways to accomplish this, but i think i got to it with the following code, what do you think? string sourceAsmName = "DllToLoadName"; Assembly sourceAsm = AssemblyLoadContext.Default.LoadFromAssemblyPath(AppContext.BaseDirectory + sourceAsmName + @".dll"); AssemblyLoadHelper.LoadReferencedAssemblies(sourceAsm); Type sourceType = sourceAsm.GetType(sourceAsmName + "." + source); MethodInfo? sourceMethod = sourceType.GetMethod("extract"); object? sourceInstance = Activator.CreateInstance(sourceType, new object[] { _config, _logger }); Task sourceTask = (Task)sourceMethod.Invoke(sourceInstance, null); _logger.LogInformati
Read more

Blazor how to generate that SHA256 check

-
So ... I see that Balzor + .NET 5 (where did Core go?!!) is now do have what i want to get my things running but of course as always something was missing, see Blazor lazy loading is just the thing i was looking for but it doesn’t work unless i reference the module/razor component library on the main project, which i exactly what is don't want. Fortunately this time everything was kind of there, just a bit trouble to do myself. See if you create a client side Razor app, you get blazor.boot.json file generated and on that file you get lazyAssembly entry which supposed to make browsers only get these assemblies if needed (can't see this working on Firefox or Chrome but that's another story), and if you list your assembly there and follow instructions in here magic happen and the page you created on your razor component library works! But, first you need to be able to calculate that sha256 value for your assembly! Which at first i couldn’t figure out how, but then found this
Read more