Well, while on this topic, the good news is that I've managed to quite easily get my work project working with VS2013. It doesn't like the work proxy so updates and the new Sign In feature don't work.
I did have to make a few changes to get my Wix project running. http://stackoverflow.com/questions/19448343/how-to-enable-wix-project-in-visual-studio-2013 Not yet noticed any new features other than a few more colours in the thing. Folders are yellow in Solution Explorer. DotCover doesn't yet support this version but everything else is very very similar to VS2012. And I can still open/build/run the solution in VS2012 after migration. (it only ads a couple of lines), so that means I can actually use it (without messing with the rest of the team!) I suppose I should actually test the output of my Wix installer project, hey? Its only a small windows service installer so should be fine. :) On Thu, Oct 24, 2013 at 10:36 AM, Ian Thomas <[email protected]> wrote: > Greg**** > > In the early days of WiX there were several UI projects (outside of the > main project), but I am not familiar with what has happened recently.**** > > Have you had a look at Oleg Shilo’s Wix# project? > WixSharp<http://www.csscript.net/WixSharp.html>uses C# scripting to manage’ > the arcane WiX framework. > **** > > However, it is way behind the WiX releases – it uses WiX v3.0.4318.0 > binaries. Conceivably the functionality in that old version of WiX would be > sufficient for many purposes (but I have not tried); because it > *doesn’t*integrate in Visual Studio it may be usable. Mike Smith (meski) may > have > some thoughts on this. **** > > CS-Script targets .NET versions up to 4.5 and I think I’m correct in > saying that Oleg Shilo lives somewhere in eastern Australia. **** > ------------------------------ > > **Ian Thomas** > Victoria Park, ****Western Australia******** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Ian Thomas > *Sent:* Thursday, October 24, 2013 8:43 AM > *To:* 'ozDotNet' > *Subject:* RE: WiX and VS2013 integration**** > > ** ** > > Bob Arnson’s latest > post<http://www.joyofsetup.com/2013/10/22/wix-v3-8-1021-0-completes-visual-studio-2013-support/> > says > it is complete as of now, and his short post has links to the issues that > have been fixed (none of those will add much to your understanding) . **** > > ** ** > > WiX v3.8.1021.0 completes Visual Studio 2013 support **** > > 22 October 2013 WiX**** > > ** ** > ------------------------------ > > **Ian Thomas** > Victoria Park, ****Western Australia******** > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Greg Keogh > *Sent:* Thursday, October 24, 2013 7:10 AM > *To:* ozDotNet > *Subject:* WiX and VS2013 integration**** > > ** ** > > I finally found a link at > http://www.joyofsetup.com/2013/09/13/getting-from-here-to-there-for-wix-v3-8/which > says that WiX 3.8 with VS2013 integration will be available by > Halloween (luckily Australians know what Halloween means thanks to *The > Simpsons*). However I can't find any other evidence that this might > actually happen, getting clear announcements on WiX isn't easy. They seem a > bit apologetic due to delays caused by end of year holidays and > Thanksgiving, but since when did holidays stop a programmer? (I do my best > coding on holidays!)**** > > **** > > As suggested, I had a quick for other IDEs over WiX, but they seem > commercial or lagging behind. In any case I don't want yet another IDE.*** > * > > **** > > They claim V3.8 will have improved > Votive<http://wixtoolset.org/documentation/manual/v3/votive/>, > which a search reveals to be the VS2013 integration (I think, even that's > vague). In VS2012 the integration of the project template, properties and > build were very nice, however the only way to edit the wizard generated WiX > source files was as plain xml. I wonder if there will be some kind of > designer over the raw source, which is what WiX desperately needs. I know > that creating a full designer experience over the complex WiX source files > would be a huge job, but it's not beyond their developer community I would > think.**** > > **** > > Greg K**** >
