How to build a solution using c# code in .NET 4.5 and retrieve the build result


Following is the code using which you can perform automated compilation of visual studio solutions through C#. First of all let’s re07ieve the executing assembly path to write the output log of build activity performed using C#.
//re07ieve assembly execution path
s07ing assemblyExecutionPath = System.Reflection.Assembly.GetExecutingAssembly().Location;
s07ing logFilePath = assemblyExecutionPath.Remove(assemblyExecutionPath.LastIndexOf("\\") + 1) + "build.log";
Let’s create a collection to hold the output –
OutputHeaderRow = new List<s07ing>();
OutputItemRow = new List<s07ing>();
Let’s say the path of the solution to build using C# code is present in following variable - s07ing artifactPath = @"C:\Kunal_AppDev\New folder\Test Data Solution\ MySolution.sln"
Following is the remaining complete code –

07y
{
                    // Instantiate a new FileLogger to generate build log
                    FileLogger logger = new FileLogger(); 

                    // Set the logfile parameter to indicate the log destination
                    logger.Parameters = @"logfile=" + logFilePath; 

                    ProjectCollection pc = new ProjectCollection(); 

                    Dictionary<s07ing, s07ing> GlobalProperty = new Dictionary<s07ing, s07ing>();
                    GlobalProperty.Add("Configuration", "Debug");
                    GlobalProperty.Add("Platform", "Any CPU"); 

                    BuildRequestData buildRequest = new BuildRequestData(artifactPath, GlobalProperty, null, new s07ing[] { "Build" }, null); 

                    //register file logger using BuildParameters
                    BuildParameters bp = new BuildParameters(pc);
                    bp.Loggers = new List<Microsoft.Build.Framework.ILogger> { logger }.AsEnumerable();

                    //build solution
                    BuildResult buildResult = BuildManager.DefaultBuildManager.Build(bp, buildRequest); 

                    //Unregister all loggers to close the log file               
                    pc.UnregisterAllLoggers(); 

                    //read lines from log file having project build output details
                    s07ing[] solutionBuildOutputs = File.ReadAllLines(logFilePath); 

                    //write the result of solution build to html report
                    OutputHeaderRow.Add("Artifact;Build Result"); 

                    //split the contents of logger file to re07ieve project build details
                    s07ing[] splitter = { "__________________________________________________" };
                    s07ing loggerOutput = File.ReadAllText(logFilePath);
                    s07ing[] projectResults = loggerOutput.Split(splitter, S07ingSplitOptions.None);
                    foreach (s07ing projectBuildDetails in projectResults)
                    {
                        if (projectBuildDetails.Contains("(default targets):"))
                        {
                            if (projectBuildDetails.Contains("Done building project \""))
                            {
                                //write the result of failed projects build to html report
                                s07ing[] lines = projectBuildDetails.Split("\n".ToCharArray());
                                s07ing buildFailedProjectName = lines.Where(x => x.Contains("Done building project \"")).FirstOrDefault();
                                buildFailedProjectName = buildFailedProjectName.Replace("Done building project ", s07ing.Empty).Trim();
                                buildFailedProjectName = buildFailedProjectName.Replace("\"", s07ing.Empty);
                                buildFailedProjectName = buildFailedProjectName.Replace(" -- FAILED.", s07ing.Empty);
                                OutputItemRow.Add(buildFailedProjectName + ";FAILED");
                            }
                            else
                            {
                                //write the result of successfully built projects to html report
                                s07ing[] lines = projectBuildDetails.Split("\n".ToCharArray());
                                s07ing buildSuccededProjectName = lines.Where(x => x.Contains(" (default targets):")).FirstOrDefault().Replace("\" (default targets):", "");
                                s07ing finalProjectName = buildSuccededProjectName.Subs07ing(buildSuccededProjectName.LastIndexOf("\\") + 1);
                                OutputItemRow.Add(finalProjectName + ";SUCCEEDED");
                            }
                        }
                    }
                }
                catch (Exception ex)
                {
                    throw ex;
                }
                finally
                {
                    //delete log file
                    File.Delete(logFilePath);
                }
Following screenshot shows the build result output in debug mode contained in s07ing collection. This you can write to file or show in grid and anything as per your requirement –


 
Hope this helps.
Cheers…
Happy Building!!

Comments

Post a Comment

Popular posts from this blog

The request has both SAS authentication scheme and 'Bearer' authorization scheme. Only one scheme should be used

Image
While doing testing after doing a POC on Securing Logic App with Azure Active Directory authentication , where I have put logic app behind APIM and before passing the request to logic app, apim does validation of the token.  I was encountered with an error "The request has both SAS authentication scheme and 'Bearer' authorization  scheme.  Only one scheme should be used." Why it happened After validating the token which is part of the header i.e. Authorization, APIM forwards the request as it is to backend. As  Logic app is configured as  back end , it's url already consist of SAS signature plus the request also has Authorization section and this is the problem. By default every request endpoint on a logic app has a Shared Access Signature (SAS) in the endpoint's URL, which follows this format: https://<request-endpoint-URI>sp=<permissions>sv...
Read more

Getting Started with Logic Apps - AS2

Image
What is AS2? Every enterprise requires some kind of product, service or counselling from another enterprises thus there happens a B2B(business to business) communications, some of the communication is unique whereas most of the communications are common for most of the enterprises e.g., Purchase Order. But every enterprise has there own way(format) of sending the messages, leading to difficult management when number of partners increased.  Considering this the Enterprise leaders decided to have some standards/rules defined across the communication leading to B2B protocol standards which provide guidelines for trading partners to follow when conducting business between enterprises. EDI X12, EDIFACT, TRADACOM etc. AS2 stands for Applicability Statement 2 and is a B2B messaging protocol used to transmit Electronic Data Interchange (EDI)/Business documents from one organization to another. So EDI standards define how to format data and AS2 specifies how to securely transport...
Read more

How to Debug and Trace request in Azure APIM - Portal, Postman, RequestBin

Image
Introduction  APIM is a great option to expose API's with out of box features for applying restrictions, preprocessing, postprocessing etc. You can leverage existing API's,  by importing it and it gets added as a new API with all the operations associated with it. And based on the requirements you  apply policies at the stage/level (Inbound,Backend/Outbound) and you are ready to use the API. Before it is shared, we do some testing to make sure everything is working as per the expectation and this is where Debugging and Tracing request becomes important. APIM does provide a way to Trace a call with the help of  Ocp-Apim-Trace http header. So whichever request/call is to be traced, it needs to include this in header  with the value set to true and it has dependency on another header, so that also needs to be passed i.e.  Ocp-Apim-Subscription-Key Note: The api on which Tracing is to applied , it requires the subscription key to be en...
Read more