{"action":"closed","issue":{"url":"https://api.github.com/repos/nopSolutions/nopCommerce/issues/590","repository_url":"https://api.github.com/repos/nopSolutions/nopCommerce","labels_url":"https://api.github.com/repos/nopSolutions/nopCommerce/issues/590/labels{/name}","comments_url":"https://api.github.com/repos/nopSolutions/nopCommerce/issues/590/comments","events_url":"https://api.github.com/repos/nopSolutions/nopCommerce/issues/590/events","html_url":"https://github.com/nopSolutions/nopCommerce/issues/590","id":127212484,"number":590,"title":"Publishing Nop without creating a publish profile and modifying the solution contents (contribution)","user":{"login":"mariannk","id":16681184,"avatar_url":"https://avatars.githubusercontent.com/u/16681184?v=3","gravatar_id":"","url":"https://api.github.com/users/mariannk","html_url":"https://github.com/mariannk","followers_url":"https://api.github.com/users/mariannk/followers","following_url":"https://api.github.com/users/mariannk/following{/other_user}","gists_url":"https://api.github.com/users/mariannk/gists{/gist_id}","starred_url":"https://api.github.com/users/mariannk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mariannk/subscriptions","organizations_url":"https://api.github.com/users/mariannk/orgs","repos_url":"https://api.github.com/users/mariannk/repos","events_url":"https://api.github.com/users/mariannk/events{/privacy}","received_events_url":"https://api.github.com/users/mariannk/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-01-18T11:59:23Z","updated_at":"2016-07-27T12:25:40Z","closed_at":"2016-07-27T12:25:40Z","body":"i really like the new way to deploy the nop source (introduced in nop 3.20) using the publishing feature of Visual Studio. \r\nBut with this feature i was forced to some manual steps:\r\n 1. Build the solution in Release Mode\r\n 2. Create a publish profile\r\n 3. Publish the Nop.Web project\r\nDoing this steps was causing to modifying the solution (because the newly create publish profile was added to the solution) and so my Mercurial cloned source of Nop was \"modified\", and this is something i don't want. \r\n\r\nFollowing the blog post of Sayed Ibrahim Hashimi \"How to extend the web publish process without modifying project contents\" (http://sedodream.com/2013/09/21/HowToExtendTheWebPublishProcessWithoutModifyingProjectContents.aspx) i was able to avoid the problem. \r\n\r\nI created a build project file that in fact does the same steps i described above using the out-of-the-box build proces made by the Nop Dev team. \r\nI like to remark that this build file doesn't change in anyway the nop build process as it's meant to be in the nop solution. \r\n\r\nThis is the code of my build file (in this case it's doing a FileSystem Publish) : \r\n\r\n... \r\n... \r\nmore info: http://www.nopcommerce.com/boards/t/27887/publishing-nop-without-creating-a-publish-profile-and-modifying-the-solution-contents.aspx"}}
{"actor":{"display_login":"AndreiMaz"}}