Timeline for Separating UI/Web Artifacts from Package?
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 5, 2012 at 5:56 | answer | added | H.Scheidl | timeline score: 1 | |
| Oct 27, 2011 at 16:08 | vote | accept | Charles Chen | ||
| Oct 13, 2011 at 15:15 | history | edited | Charles Chen | CC BY-SA 3.0 |
Added more justification..
|
| Oct 12, 2011 at 19:58 | answer | added | Charles Chen | timeline score: 1 | |
| Oct 12, 2011 at 18:02 | comment | added | James Love | Blog all this somewhere when you get results, there'll be plenty of people who'll benefit from your findings, I guarantee it. | |
| Oct 12, 2011 at 18:00 | comment | added | Charles Chen |
The BeforeLayout target is not enough as it does the copy fine and the file ends up in the package, but the file is not added to the manifest. As far I can tell, the manifest is not generated as a part of the msbuild process so there is no way to control how it's generated aside from the basic manifest merge as it doesn't seem like new files are picked up automatically and added to the manifest dynamically. Wondering if there are more sophisticated ways to manipulate the manifest now.
|
|
| Oct 12, 2011 at 15:43 | comment | added | Charles Chen | I'm now thinking that I can use the BeforeLayout MSBuild target to perform custom file layout before packaging. Challenge is that the documentation on how to do this is severely lacking (non-existent?). MSDN only gives some fairly generic references: msdn.microsoft.com/en-us/library/ee231560.aspx, msdn.microsoft.com/en-us/library/ee231572.aspx and there's not much on the Internet on this topic (or my Googlefu is weak....). Will keep this thread posted. | |
| Oct 11, 2011 at 22:03 | history | tweeted | twitter.com/#!/StackSharePoint/status/123881519952576512 | ||
| Oct 11, 2011 at 21:04 | comment | added | Charles Chen | Yes. With WSPBuilder, again using XCOPY on pre- or post-build, I just copy the dependent binaries to the /GAC directory of the Package project and WSPBuilder handles generation of the manifest. Same with .aspx, .css, .js, and other artifacts -- these just get xcopied to /14/TEMPLATE/{TARGET_PATH} in the solution tree. But I'm not necessarily looking for the same exact workflow -- just some practical, automated way of allowing for the same type of separation and be able to keep web artifacts like .aspx files in a web project and not the package until it's time to build the package. | |
| Oct 11, 2011 at 20:55 | history | edited | Charles Chen | CC BY-SA 3.0 |
Added some text.
|
| Oct 11, 2011 at 20:51 | comment | added | James Love | I need to check: Do you still deploy things like filesystem elements and assemblies with WSPs in your separated model, yes? | |
| Oct 11, 2011 at 20:49 | history | edited | Charles Chen | CC BY-SA 3.0 |
Added details and fixed grammar.
|
| Oct 11, 2011 at 20:30 | history | asked | Charles Chen | CC BY-SA 3.0 |