How does an ExportLogic package differ from a Visual Studio publish?


#1

Anyone know off the top of their head?


#2

No, but one likely difference is that EWL logic packages do not include configuration files, which are put into separate packages. This approach allows us to use the same logic package for any kind of installation (live, testing, staging, etc.).


#3

One big difference is that ExportLogic includes Ewf/Styles, and Publish packages do not, by default.


#4

Here are all of the differences. What does ISU do to include these files? I want to accomplish it with VS Publish without getting into an arms race with JS files deep in the folder structure.

Export Logic has debug=false in web config.

Export Logic has, but VS Publish does not:
/FileUploader/js and images
/ThirdParty/js and txt and css
/Styles
/VersionedStaticFiles

ExportLogic does, but shouldn’t, include /PublishProfiles and Web.Debug.config and Web.Release.config.


#5

The Development Utility’s ExportLogic code is here:

https://enduracode.kilnhg.com/Code/Ewl/Group/Canonical/Files/Development%20Utility/Operations/ExportLogic.cs?rev=tip#153