Packaging C# .NET Applications for Profiling

Important note: Only C# .NET projects are supported at this time, and the Web Site project type is not currently supported.  
In order for PaaSLane to profile C# .NET applications, they must be packaged as a .zip file containing all source, built assemblies, and referenced 3rd party assemblies.  In most cases, this just involves building your Visual Studio solution (.sln) as you normally would, and then creating a .zip file from the contents of the solution root directory after that build.
Packaging C# .NET (C#) Applications for Profiling:
- The application must be packaged as a .zip file
- This zip file needs to contain:
     - All source code, config files, and solution/project files (.sln, .csproj, .cs, .config, etc.).
     - All 3rd Party assembly (.dll) files that are referenced by the application.
            - This includes Microsoft assemblies that are not part of a standard .NET Framework installation. It is recommended to set CopyLocal=True for 3rd party assembly references to ensure they get included as part of the project output.
     - All solutions included in the .zip for PaaSLane profiling should be built in Debug mode such that .dll/.pdb files are present in the project output directories.
     - All the above listed files should be included in the .zip in the same structure in which they were built.
Known issues with C# .NET profiling:
- Visual Studio solution files must refer to C# projects using relative path, and not absolute path. (Referring to projects with absolute paths is not good practice, and can render the solution not portable between environments.)
- Silverlight applications are not currently supported.
- Web Site projects are not currently supported.  (This exclusion does not include Web Application projects.)
- Applications cannot have references to assemblies that contain recursive type-definitions. (One known instance of this is MassTransit.dll.)


Powered by Zendesk