Quantcast
Channel: wixsharp Discussions Rss Feed
Viewing all 1354 articles
Browse latest View live

New Post: Installing to %PersonalFileFolders%

$
0
0
First error is due to the fact that you are using my code from UnitTest class but your code is most likely a static class/method. You need to make Project_WixSourceGenerated static.

Second error is because the code I gave you is using the latest codebase extension method HasAttribute. In your case you need to modify the code to use the older signature:
   .Where(x => x.HasAttribute("Name", v => v == "PersonalFolder"))
For the binaries you need either to clone the repository on your PC with Git client or download from the browser:
Image

New Post: Installing to %PersonalFileFolders%

$
0
0

I am sorry, but something isn’t working. I had the static issue resolved but the

Var comp = dir.Element(“Component”);

Returns null.

Robert Race, PE

Race Engineering Assoc

4851 Four Seasons Ct

Eagan, MN 55122

t: 612.670.7009

e: [email removed]

New Post: Installing to %PersonalFileFolders%

$
0
0
You need to start using wiki. Your mail client prevents you from sending attachments and images. It also exposes your personal information. See it for yourself: https://wixsharp.codeplex.com/discussions/642263

Anyway, you need to find the XML 'component' of that directory element, which generates the error and inject the missing elements. In the code I provided the search algorithm is designed for my Wix# project structure. In your case you may need to adjust it to match your project structure. I can only be sure in the workaround that I provided when it is applied to the test code you sent me. You can get your adjusted sample back from here.

New Post: How can I add attributes to a Dir?

$
0
0
Well, it turns out that this works completely fine. Apparently, the command prompt doesn't dynamically update environment variables. I didn't realize that yesterday, and it tripped me up. My bad.

New Post: Installing to %PersonalFileFolders%

$
0
0

I downloaded and built the binary files. It works as it should now.

Thank you for your help. You have done a good job of creating this application.

Robert Race, PE

New Post: Authentication doesn't set in iis for web application if try to assign it with parameter

$
0
0
in my installer i have:




WebDirProperties = new WebDirProperties(serviceName)
                        {
                            AttributesDefinition ="[AUTHDEFINITION]" 
// "AnonymousAccess=yes; WindowsAuthentication=no"
                        },

This authentication type is defined by user in ui and i check that this parameter is really set into "AnonymousAccess=yes; WindowsAuthentication=no"
But it doesn't actually set authentication as requested (but derived it from parent web site)! If i hard code this value it set it correctly! What can be the problem and how it could be resolved?

New Post: Authentication doesn't set in iis for web application if try to assign it with parameter

$
0
0
Check your WXS and you will see that your [AUTHDEFINITION] is not embedded in it. You cannot set AttributeDefinition to the WIX proiperty as WiX has no idea about "AttributesDefinition".

Most likely you want to bind WiX attributes individually to the formatted properties.
AttributesDefinition = "AnonymousAccess=[AUTHACESS]; WindowsAuthentication=[WINAUTH]"
However I am not even sure WiX allows binding these attributes to properties. Most likely it requires them to be hard coded.

I just checked quickly and no you cannot set them dynamically they have to be hard coded to 'yes' or 'no'. This is what you should check if you are trying to adjust WiX attributes directly: http://wixtoolset.org/documentation/manual/v3/xsd/iis/webdirproperties.html.

New Post: Authentication doesn't set in iis for web application if try to assign it with parameter

$
0
0
how do you know that it can't be set dynamically?

New Post: Authentication doesn't set in iis for web application if try to assign it with parameter

$
0
0
It's not necessarily obvious. The WiX/MSI documentation almost never reflects it directly but usually YesNoValues cannot by bound to the MSI properties.

Saying that you should not take my word for this and do the testing and see if binding is possible.

New Post: later to define install dir

$
0
0
Hi,

I need to define installation directory depending on parent web site location + web application name.

I tried to use:

var project = new ManagedProject("MyProduct",
            new Dir("UNDEFINED",
and then set INSTALLDIR in custom action:
new ManagedAction(@"SetInstallDir", Return.check, When.Before, Step.InstallFiles, Condition.NOT_Installed)


and "SetInstallDir" function assign INSTALLDIR into a path which depends on 2 other properties... but unfortunately it creates "UNDEFINED" directory on current disc.

I also see that InstallDir has correct value in one helping message boxes goes from project template...

How to set it?

Also, actually I need to use physical path of parent web site to which I install application, may be it's some standard way to use it?

New Post: How to implement Instances with Wix#?

$
0
0
I'm not sure you understand me correctly, because I cannot find something about multiple instances installations. I meant that I should be able to install my application several times with different names and locations.
In wix it's realised as followed:
<InstanceTransforms Property="INSTANCEID">
<Instance Id="I01" ProductCode="{GUIDGOES-HERE-4731-8DAA-9E843A03D482}" ProductName="My Product 01"/>
<Instance Id="I02" ProductCode="{GUIDGOES-HERE-4f1a-9E88-874745E9224C}" ProductName="My Product 02"/>
<Instance Id="I03" ProductCode="{GUIDGOES-HERE-5494-843B-BC07BBC022DB}" ProductName="My Product 03"/>
</InstanceTransforms>

then you need to define registry settings for each instance etc etc.
Is this functionality implemented somehow simpler in wix#?

Or generally how to install several instances on the same machine?

New Post: How to implement Instances with Wix#?

New Post: later to define install dir

$
0
0
This may help: sample "<WixSharp>\Wix# Samples\InstallDir" shows how to overwrite the default installdir. In the sample it is set from the Install_CustomDirectory.cmd batch file but you can do the same from your custom action.

But the easiest way is to modify the InstallDir dialog to implement your "path generation" instead of going with the custom action.

New Post: Installer requires .net 3.5 features to be installed

$
0
0
If add CLR window into installer it requires .net framework 3.5

Also when you run such .msi it requires .net 3.5 or in my case it was enough to install .net 3.5 server features :( This is very frustrating because we force user to install unnecessary feature to launch installer.

Do you know how to avoid this problem? Include .dll into installer project?

New Post: later to define install dir

$
0
0
ohh, in my case install dir depends on what site user is selected and actually installdir = physical folder of parent web sire + service name
(service name is also selected by user during installation)

New Post: Installer requires .net 3.5 features to be installed

$
0
0
Also when run it on Windows Server 2012 it doesn't show controls on window.
Only when I run it from cmd which was run under Administrator it shows controls

New Post: Installer requires .net 3.5 features to be installed

$
0
0
.NET today is a part of the operating system. In fact MS installs it to the OS as part of the update policy on the older systems. Even WiX team doesn't consider .NET dependency as a show-stopper any more. You can have a launch condition that can check the version of .NET present. Even more, you can use silent bootstrapper that can download and install the required .NET automatically. That is why I found "NO .NET" requirement being a bit "artificial". But I am not going to argue about what is appropriate for your project and what is not.

Anyway... if it is your requirement that target system doesn't have .NET installed then you cannot use managed custom actions at all. Meaning the you cannot benefit from Wix# custom actions support and need to go back to the old fashion native msi. It also means that it is no longer a Wix# topic and you need start studying MSI/WiX/C++. You will need to:
  • Implement a custom action dll (C++ topic).
  • Embed the dll into Wix# project. It's simple: with WixSharp.Binary.
  • Then you need to find out how to implement invoking the custom action (WiX topic).
  • You will need to embed the WiX XML CA scheduling element(s) in the Wix# project with "XML Injection". See Wix# samples.

New Post: later to define install dir

$
0
0
If you use managed custom action then you just assign assign the installdir new value:
session["INSTALLDIR"] = <physical folder of parent web sire> + <service name>;
But you decided not to use .NET so you will need to do this in raw MSI/WiX.

New Post: later to define install dir

$
0
0
It's misunderstanding. I used .net, but for some reason it doesn't work. (see the first post).

New Post: Installer requires .net 3.5 features to be installed

$
0
0
I'm talking only about .net 3.5.
In my case it's .net 4.0 is a prerequisite for working of our product. Moreover usually there is .net 4.5 installed on all our servers. Nut installer with custom CLR UI requires .net 3.5
Viewing all 1354 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>