bal:Condition is provided in bundle.wxs file. But the condition is not getting evaluated and error message is not shown. This is the code I’ve provided
<bal:Condition Message="This Setup requires .NET Framework 4.7, please download and install it to proceed further.">
1=2
</bal:Condition>
Related
Error 1053 - Service do not respond to the start or control request in a timely fashion
I am installing solr 9.1.1 version using nssm. The path to executable was repeatedly setting to nssm.exe path. But I explicitly changed to solr.cmd path.
Now I am getting another error - Error 1053 - Service do not respond to the start or control request in a timely fashion
Path seems fine. I don't find any issue and don't understand why it is happening.
I was able to solve the error. The issue was I downloaded wrong package.
Downloaded latest from https://solr.apache.org/downloads.html.
earlier package was incomplete - without required jar files.
so downloading new package worked.
As the title says, I'm having trouble getting Fody, and the plugin Fody.PropertyChanged, to work in .NET Core 3.0, or any .NET Core version. Reading the issues on the respective GitHub pages doesn't answer my question, nor am I able to find any relevant answers.
Once installed I cannot run my WPF project anymore and I am given the following error:
The target process exited without raising a CoreCLR started event.
Ensure that the target process is configured to use .NET Core.
This may be expected if the target process did not run on .NET Core.
The program '[21820] CalculationToolsApp.exe' has exited with code -2147450749 (0x80008083).
Any suggestions?
EDIT: I found out that I (maybe) cant use "Fody.Costura" with "Fody.PropertyChanged" like this in the FodyWeavers.xml file:
<Weavers>
<PropertyChanged />
<Costura />
</Weavers>
Which shouldn't be a problem because with .NET Core I can create a single file application anyway. Removing the Costura reference from the FodyWeavers.xml solved my problem!
It should work. Fody is compatible with .NET Standard.
Create a new WPF app using the WPF App (.NET Core) template in Visual Studio 2019 or using the dotnet new wpf command
Install the Fody and PropertyChanged.Fody NuGet packages
Add a file named "FodyWeavers.xml" with the following contents to the project:
<Weavers>
<PropertyChanged />
</Weavers>
Build
If you then decompile the assembly using a decompiler such as for example dotPeek, you should see the injected code as expected, e.g.:
public string GivenNames
{
// Method get_GivenNames with token 06000009
get
{
return this.<GivenNames>k__BackingField;
}
// Method set_GivenNames with token 0600000A
set
{
if (string.Equals(this.<GivenNames>k__BackingField, value, StringComparison.Ordinal))
return;
this.<GivenNames>k__BackingField = value;
this.<>OnPropertyChanged(<>PropertyChangedEventArgs.FullName);
this.<>OnPropertyChanged(<>PropertyChangedEventArgs.GivenNames);
}
}
Costura didnt work in wpf with .net core 3.1 for me either.
In .net core 3.1 you can use this instead:
Build -> publish -> create profile -> Edit "Configuration"
Target Runtime = win-x64 (or what ever target system you want, but NOT "portable")
expand "File Publish Options"
check: Produce single file
save
When you now choose build -> publish -> publish button it will create the single file.
It seems to be that they stopped the costura project because of the "Single-file executables" feature of .net core. Though this feature is still behind costura because you have to set a target runtime.
https://github.com/Fody/Costura/issues/442
In dotnet core 3 there are two new features
Single-file executables
Assembly linking
With these features included in the dotnet tool set, the value
proposition of Costura is greatly diminished. With that in mind I
think long term Costura should cease to be used as people transition
over.
Please comment with any input.
Plan:
disable issues
PR will still be accepted but only for bug fixes
add note to readme
add note to nuget description
write a warning in
update for .NET 5:
for .NET 5 and the current visual studio version 16.10.2 the wizard changed. I could not get this to work with the wizard anymore though i checked the options for single file etc.. But using the console worked: tools -> command line -> developer command prompt -> enter this:
dotnet publish -r win-x64 --self-contained true -p:PublishSingleFile=true -p:IncludeAllContentForSelfExtract=true
.NET 5 not compiling to single file executables
I installed plugin "sonar-report-plugin" to get PDF report from sonar.
I have done all required setup in sonar for this plugin.
Now I just want to know what command to execute to get the report as "sonar-runner report" command is no longer functional in sonarqube5.2.
Indeed for technical reasons the Report plugin could not be kept compatible with SonarQube 5.2. Support is back in version 5.3, which first release candidate has been published today.
http://docs.sonarqube.org/display/SONAR/Release+5.2+Upgrade+Notes
I am getting the below exception while trying to connect a esx-i 5 machine using vijava vsphere API.
vijava is the VMware Infrastructure JAVA API.
I am using the VI Java API 5.5 Beta vijava55b20130927.
What might be the root cause of this issue.
java.rmi.RemoteException: VI SDK invoke exception:java.rmi.RemoteException: VI SDK invoke exception:org.dom4j.DocumentException: **Error on line 4 of document : Open quote is expected for attribute "{1}" associated with an element type "rel".** Nested exception: Open quote is expected for attribute "{1}" associated with an element type "rel".|
[12:02:07:318]|[12-18-2014]|[SYSOUT]|[INFO]|[135]|: at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:131)|
[12:02:07:318]|[12-18-2014]|[SYSOUT]|[INFO]|[135]|: at com.vmware.vim25.ws.VimStub.retrieveServiceContent(VimStub.java:1437)|
[12:02:07:318]|[12-18-2014]|[SYSOUT]|[INFO]|[135]|: at com.vmware.vim25.mo.ServiceInstance.<init>(ServiceInstance.java:100)|
[12:02:07:318]|[12-18-2014]|[SYSOUT]|[INFO]|[135]|: at com.vmware.vim25.mo.ServiceInstance.<init>(ServiceInstance.java:84)|
If you will switch to using YAVIJAVA I can help.
The Beta version of VIJAVA has a bug where only a RemoteException is ever thrown. That bug is fixed in YAVJAVA 5.5.08-DEVELOPMENT or newer which as of this comment is only available on github (older versions in maven have this bug)
YAVIJAVA includes logging via log4j and if you enable debug logging when you run the command you can even get the XML payloads that are coming and going from the server which I can use to help you trouble shoot this problem.
I'm a newbie in cakephp, I'm trying to upgrade cakephp to the latest version.
I install the fresh cakephp 1.3 on my computer and the upgrade it to cakephp 2.1.
I use shell to upgrade, but after I run 'upgrade all' command, I saw two error:
Warning Error: chmod(): Operation not permitted in [/var/www/cakephp-1.3/lib/Cake/Utility/Folder.php, line 639]
Warning Error: touch(): Utime failed: Operation not permitted in [/var/www/cakephp-1.3/lib/Cake/Utility/Folder.php, line 640]
I think it has upgraded complete. Because I see the message from terminal like this:
Done updating /var/www/cakephp-1.3/app/Console/cake.php
Done updating /var/www/cakephp-1.3/app/Console/Command/AppShell.php
Running components
Running exceptions
Then I refresh my app and I got some errors:
http://flic.kr/p/bwUpwY
Then I delete 'cake' directory, and the error message has changed:
http://flic.kr/p/bKP7Te
So now I don't know what to do next, because I did many ways but still not make it work.
So anybody please tell me what I did wrong and how can I upgrade cakephp successful.
Thanks in advance.
This looks like you have permissions issues on some of the directories that the CakePHP migration script expects to be writable.
This could lead to the migration failing on some parts and leaving a partially broken install after it completes.