Open jzajac2 opened 8 years ago
Which version of WiX v4?
I updated the ticket - I was actually using 3.10. Having issues binding to 4.0 now so I'll leave it at that for now.
Please attach a snippet of authoring you're using and a log showing the problem.
Snippet of using iis extension:
I assume you mean verbose MSI log, so I attached that. msixexec-log.zip
Hello I am facing same issue in wix 3.10. Is there any solution available for this issue?
Hi, I'm facing same issue in wix 3.10. Is there any update for this bug?
The bug is open waiting for someone to investigate it and develop a fix for it.
If someone can point me in the right direction I'll have go, but I haven't even been able to figure out how to build the iis extension project.
Extension code lives under https://github.com/wixtoolset/wix3/tree/develop/src/ext/IIsExtension. Custom actions live under https://github.com/wixtoolset/wix3/tree/develop/src/ext/ca/serverca. Build wix.proj
from the root.
@barnson pointed to wrong tree. You want WiX v4:
Hi, The build steps for wix don't seem to work and they're confusing, how many/ which versions of VS do I need to compile it? additionally the RC.exe command in the build seems to default, point at the one in c:\windows which is a completely different tool. But I finally got the command line build operational after installing multiple VS's 2010/2012/2013 and multiple windows SDK's, and renaming my rc.exe in the c:\windows folder.
Where is the sln file for the extensions, I can only find the csproj files? When I open the csproj file the refs to the external projects all break and VS complains that I can't readd them. @robmen I can't really use v4 as its not released yet and I need this fix asap
@hegsie, please describe what was wrong with the doc. You don't need more than one version of Visual Studio; http://wixtoolset.org/development/building-wix/ describes that.
There's no solution because we don't use solutions to build. You can open the projects individually to edit and debug and build from the command line.
@hegsie Focus is moving to WiX v4. Fix needs to be taken there first and we'll discuss what goes into WiX v3.14 case by case. We're generally not taking new work in WiX v3.14 that isn't to help migrate users to WiX v4.0.
@barnson The docs are just a little ambiguous about the correct version of VS, and the RC.exe issue needs to be documented. Otherwise I'm in a building state now and will take a look when I have some spare time.
@robmen unless I've missed something I haven't seen a release of v4, I'd love to migrate and use RType but i need this fix yesterday and I found a solution to my issue by convincing wix to think a dummy vdir is in place use an alias of '\' in the vdir
WiX v4 has several weekly releases but needs our focus to get production ready. That's why we're shifting focus.
Also, RType isn't part of WiX v4. It's still a prototype for us to explore but won't fit in WiX v4 if we want to get WiX v4 out in any reasonable amount of time.
PS: I don't have an rc.exe
anywhere under my WindowsFolder on Windows 8.1 and Windows 10. You might want to investigate what put it there on your machine, @hegsie.
WiX 3.10, VS 2013, Win7x64. Installing my setup under IIS 6.1 on Server 2008R2 Documentation claims that MimeMap elements can be added under WebSite elements, however doing so results in no MIME type created in the WebSite in IIS.
For what its worth: It appears the IIsMimeMap table is adding the correct values to the columns: ParentType=2 and ParentValue={IDOfMyWebSite}. where 1=vdir 2=website
Adding under WebVirtualDir works fine. However, I have run into deployments without explicit virtual directories or applications in IIS (via Add Application, Add Virtual Directory). I honestly don't understand the value and can adapt to using WebVirtualDir, however I am able to add MIME types directly to a Website using InstallShield just fine, so I figured it is probably a desired configuration for others.