Geek asks and answers

Is it possible to rename the created class and assembly (for Visual Studio) for a custom WiX C # action?

When I use WiX 3.x with Visual Studio 2010 to create a Windows Installer XML file “C # Custom Action Project” called “MyCustomActions”, it generates the following files:

"CustomAction.config", "CustomAction.cs" and the project file "MyCustomActions.csproj".

We use an assembly naming scheme that includes our company name, so we change the assembly name to something like: CompanyName.ProductName.MyCustomActions

At the same time, we are changing the default namespace and the actual namespace for the CustomActions class for CompanyName.ProductName.MyCustomActions to match the assembly name.

Can this be done without changing any other file names or classes?

What I am interested in is the use of the CustomAction.config file - somehow the name should be associated with the name of the output assembly? I'm not sure how "CustomAction.config" will be used.

Also: the CustomAction.cs file contains a class called "CustomActions" (note the plural), and our naming convention says that the code file for the class must have the same name as the class itself, so for example, we would rename code file in "CustomActions.cs". I'm sure OK ... Is that?

Finally, if we renamed the CustomAction class to another, would everything be all right? Again, I'm just worried about his attitude to "CustomAction.config".

, : "CustomAction.config" , ?

, .

+5
2

WIX, , - , "CustomAction.config" ( WIX) VS "". - .

CLR ( ) , dll.

dll API .Net.

+5

.NET- . , CLR 2.0 (.NET framework 2.0 3.5), .NET Framework 4.0. , configure , Framework 4.0.

<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v2.0.50727"/>
<supportedRuntime version="v4.0"/>

, .

0

More articles:


All Articles