My latest attempt at a workable configuration (Win32) is this one found on kodewerx.org: http://www.kodewerx.org/wiki/A_Brief_Introduction_To_XULRunner:_Part_2 [dated 2010].
My config is as follows:
c:\program files\xulrunner\xulrunner.exe ..et all..
c:\program files\myapp\application.ini
I have added c:\program files\xulrunner to the system PATH.
From the command prompt xulrunner.exe executes and throws up its default help page.
So xulrunner.exe runs.
I have used Mozilla's Dev Org app for jump starting add on development: http://www.mozdev.org/projects/wizard/
I used a Application configurator which has provided me with a large number of files, in a typical moz/chrome layout.
c:\Program Files\MyApp\application.ini
c:\Program Files\MyApp\defaults\preferences\prefs.js
c:\Program Files\MyApp\chrome.manifest
c:\Program Files\MyApp\chrome\content\[*.xul|*.js]
c:\Program Files\MyApp\chrome\locale\en-US\*.dtd
c:\Program Files\MyApp\chrome\skin\*.css
I am uncertain about the minimum/maximum Gecko versions to specifiy at the current date: I have this for the moment, in application.ini:
[App]
Name=MyApp
ID=myapp#stainsby.ca
Version=0.1
BuildID=0001
Vendor=Stainsby
[Gecko]
MinVersion=1.9.2.0
MaxVersion=28.0.*
Any ideas?
Related
I am getting the below error while attempting to launch the UI Automator Viewer tool via command prompt.
C:\Users\getta\AppData\Local\Android\Sdk\tools\bin>uiautomatorviewer
-Djava.ext.dirs=..\lib\x86_64;..\lib is not supported. Use -classpath instead. Error: Could not create the Java Virtual Machine. Error: A
fatal exception has occurred. Program will exit.
I was googling and it suggested to downgrade Java to v8...any other workarounds apart from that??
Set your all android path properly.
Add a variable in system environment as mention below.
ANDROID_HOME : C:\Users[Your login name]\AppData\Local\Android\Sdk (Or any PATH that your android SDK located)
JAVA_HOME: C:\Program Files\Java\jdk1.8.0_172
ANDROID_SWT : C:\Users[Your login name]\AppData\Local\Android\Sdk\tools\lib\x86_64
ANDROID_PLATFORM_TOOLS : C:\Users[Your login name]\AppData\Local\Android\Sdk\platform-tools
Add below mention Path in Path Variable in the system environment.(If your SDK located in: C:\Users[Your login name]\AppData\Local\Android\Sdk\ )
C:\Program Files\Java\jdk\bin;
C:\Users[Your login name]\AppData\Local\Android\Sdk\tools\bin;
C:\Users[Your login name]\AppData\Local\Android\Sdk\tools;
C:\Users[Your login name]\AppData\Local\Android\Sdk\platform-tools;
C:\Program Files\nodejs\node_modules\npm\bin;
C:\Users[Your login name]\AppData\Local\Android\Sdk;
C:\Users[Your login name]\AppData\Local\Android\Sdk\tools\lib\x86_64\swt.jar;
You don't need to downgrade Java version, just have jdk1.8 and then set your JAVA_Home to there
I have version 10 in my system but also have the other jdks. As you can see in the attached docs, I have version 8 & 10 and the system knows version 10. But I set the JAVA_HOME to jdk 1.8 and it's working well.
JDK versions
What shows by command "java -version"
While building the Windows environment for OsQuery (on my Windows 10 VM) from their website(link: https://osquery.readthedocs.io/en/stable/development/windows-provisioning/), I am getting the msb1009 error during the phase where I have to run the tools\make-win64-binaries.bat command. I get the following result after running that command:
CMake Error at CMakeLists.txt:402 (project):
Failed to run MSBuild command:
C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/MSBuild/15.0/Bin/MSBuild.exe
to get the value of VCTargetsPath:
Microsoft (R) Build Engine version 15.7.179.6572 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.
MSBUILD : error MSB1009: Project file does not exist.
Switch: VCTargetsPath.vcxproj
Exit code: 1
-- Configuring incomplete, errors occurred!
See also "C:/Windows/System32/osquery/build/windows10/CMakeFiles/CMakeOutput.log".
Microsoft (R) Build Engine version 15.7.179.6572 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.
MSBUILD : error MSB1009: Project file does not exist.
Switch: osquery.sln
[-] osquery build failed.
I have been trying to make the osquery.sln file using that command and have looked online for solutions but without any success. Any help would be much appreciated!
Thanks in advance
Edit: Here is the output of running tools\make-win64-dev-env.bat and tools\make-win64-binaries.bat
tools\make-win64-dev-env.bat
tools\make-win64-dev-env.bat (contd..)
tools\make-win64-binaries.bat
Could you paste the full output of running the tools\make-win64-dev-env.bat and tools\make-win64-binaries.bat? Also have you tried closing out your shell and re-opening, or even worse -- reboot the system?
I ask because, as you note, it seems like the solution file never gets generated, which usually means there was either a missing dependency during provision, or some other issue when the script first ran. On first provision it's typically the case that a system reboot is needed, as Visual Studio community typically requires one. Further, we set a few shell environment variables that are leveraged during the build process, however those are supposed to be set at the end of the provisioning script.
Also feel free to hit us up in our Slack and check out the #windows channel :)
After a lot of code reading, researching online and trial and error, I found out that after a clean OS install, one would need to install git and then immediately clone the osquery repository on the user desktop rather than System32. This worked fine, at least for me. Just make sure to switch directories when opening command line with administrator mode.
Update:
I have reproduced the same Error with a new empty VS2015 WebApplication project.
Added a connectionString to a new empty SQL database
Added a sql-script file to the solution and selected publish... in the publish wizard.
Example of web Publish wizard with included Update script.
I will get the same error building a web deployment package or web deploy .
Original post:
The "SqlScriptPreprocessSqlVariables" task failed unexpectedly. This happens when I use publishing wizard or MSBuild with a profile where the Update Database is selected. On a newly installed machine with only VS2015 Update1 and also on our build server with Team Fondation Server 2015 Build Agent. The same publish profile works in our VS2013 environment.
System.TypeLoadException: Signature of the body and declaration in a method implementation do not match.
Type: 'Microsoft.Web.Publishing.Tasks.SqlScriptPreprocessor.SqlCommandExecuter'.
Assembly: 'Microsoft.Web.Publishing.Tasks, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
at Microsoft.Web.Publishing.Tasks.SqlScriptPreprocessor.SqlScriptPreprocessSqlVariables.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask>d__26.MoveNext()
Here is the same error but from the Build Agent in the new build system. I got the same error runnig XAML build on the new Agent.
##[error]C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Deploy\Microsoft.Web.Publishing.MSDeploy.Common.targets(119,5): Error MSB4018: The "SqlScriptPreprocessSqlVariables" task failed unexpectedly.
##[error]System.TypeLoadException: Signature of the body and declaration in a method implementation do not match. Type: 'Microsoft.Web.Publishing.Tasks.SqlScriptPreprocessor.SqlCommandExecuter'. Assembly: 'Microsoft.Web.Publishing.Tasks, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
##[error] at Microsoft.Web.Publishing.Tasks.SqlScriptPreprocessor.SqlScriptPreprocessSqlVariables.Execute()
##[error] at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
##[error] at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()
This is how I fixed the webdeploy packaging problem. This is not a solution I recommend but it works on my machine and on the build server.
Locate the file Microsoft.Web.Publishing.MsDeploy.Common.targets
This is the location on my machine:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Deploy\ Microsoft.Web.Publishing.MsDeploy.Common.targets
On row 117 and forward I commented out the following section.
<!--<SqlScriptPreprocessSqlVariables
UnsupportedKeywords="$(MsdeploySqlUnsupportedCommand)" CheckForUnsupportCommands="$(CheckSqlScriptForUnsupportedCommands)"
TreadSqlScriptUnsupportedCommandsAsWarning="$(TreadSqlScriptUnsupportedCommandsAsWarning)"
SqlScriptFile="%(_DatabasesToPackageForSQL.SourcePath)"
DestinationGroup="%(_DatabasesToPackageForSQL.DestinationGroup)"
ResolveIncludes="$(SqlScriptPreProcessResolveIncludes)"
BatchDelimiter="$(SqlScriptPreProcessBatchDelimiter)"
Condition="$(EnableSqlScriptVariableParameterize) And '%_DatabasesToPackageForSQL.SourcePath)' != '' And Exists('%(_DatabasesToPackageForSQL.SourcePath)') ">
<Output TaskParameter="List" ItemName="_DatabasesToPackage_SqlVariables" />
</SqlScriptPreprocessSqlVariables>-->
I recently faced the same issue and I solved it installing the latest version of "SQL Server Data Tools" and restarting the machine. As #JimAho mentioned, the problem is related to SQL Server Data Tools version installed.
Here you could download it
Don't forget to restart the machine.
Still not quite satisfied with these solutions, I did some research and the least invasive approach I can see is simply registering the assembly in the GAC.
Run VS Command Prompt as Administrator
Hit Windows Start
type "Developer"
Right Click "Developer Command Prompt for VS 2017"
Select Run as Administrator
Run the following command (Replace Enterpise with your installation, e.g. Professional, BuildTools, Community):
gacutil /i "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\Extensions\Microsoft\SQLCommon\130\Microsoft.SqlServer.BatchParser.dll"
I was using msbuild build my sln and get error message "couldn't find 'AxImp.exe' which already exists under %Program files (x86)%\Microsoft sdks\windows\v8.1A. but seems it find sdk from v8.0A, output info point out the error was in Microsoft.Common.targets file(code see below). I didn't found where the "TargetFrameworkSDKToolsDirectory" was defined, anyone can help me?
environment: winblue(4.5.1 sdk v8.1A) without visual studio.
<ResolveComReference
TypeLibNames="#(COMReference)"
TypeLibFiles="#(COMFileReference)"
ResolvedAssemblyReferences="#(ReferencePath)"
WrapperOutputDirectory="$(InteropOutputPath)"
IncludeVersionInInteropName="$(IncludeVersionInInteropName)"
KeyContainer="$(KeyContainerName)"
KeyFile="$(KeyOriginatorFile)"
DelaySign="$(DelaySign)"
StateFile="#(_ResolveComReferenceCache)"
TargetFrameworkVersion="$(TargetFrameworkVersion)"
TargetProcessorArchitecture="$(ProcessorArchitecture)"
NoClassMembers="$(ComReferenceNoClassMembers)"
Silent="$(ResolveComReferenceSilent)"
EnvironmentVariables="$(ResolveComReferenceEnvironment)"
**SdkToolsPath="$(ResolveComReferenceToolPath)"**
ExecuteAsTool="$(ComReferenceExecuteAsTool)"
MSBuildArchitecture="$(ResolveComReferenceMSBuildArchitecture)"
ContinueOnError="$(ContinueOnError)">
<**ResolveComReferenceToolPath** Condition="'$(ResolveComReferenceToolPath)' == ''">$(**TargetFrameworkSDKToolsDirectory**)</ResolveComReferenceToolPath>
Depends on the version and platform you're targeting, but latest is at C:\Program Files (x86)\MSBuild\12.0\Bin\Microsoft.NetFramework.CurrentVersion.props, follow your imports, i.e. <Import Project=".targets" />. To get the values run MSBuild with /v:diag and all evaluated properties will be dumped and the start.
what ended up working for me was installing:
Windows Software Development kit (SDK) for windows 8
even though I'm on widows server 2016
https://developer.microsoft.com/en-us/windows/downloads/windows-8-sdk
I guess the clue was in my error:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(2428, 5): error MSB3086: Task could not find "LC.exe" using the SdkToolsPath "" or the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v8.0A\WinSDK-NetFx40Tools-x86". Make sure the SdkToolsPath is set and the tool exists in the correct processor specific location under the SdkToolsPath and that the Microsoft Windows SDK is installed
I have a problem install ioncube on windows plesk control panel.
I used the thread-safe version of PHP and download Windows VC9 (x86) ioncube.
I Put the Loader files in C:\Program Files (x86)\Parallels\Plesk\Additional\PleskPHP5\ext
I do Edit the file C:\Program Files (x86)\Parallels\Plesk\Additional\PleskPHP5\php.ini and before any other zend_extension_ts lines ensure that the following is included:
zend_extension_ts = "C:\Program Files (x86)\Parallels\Plesk\Additional\PleskPHP5\ext\ioncube_loader_win_5.2.dll"
and Restart the IIS server software.
but not run ioncube. :(
Additional Information:
Loader is at: C:\Program Files
(x86)\Parallels\Plesk\Additional\PleskPHP5\ext\ioncube_loader_win_5.2.dll
Loader OS code: win
Loader architecture: x86
Loader word size: 32
Loader PHP version: 5.2
Loader thread safety: Yes
Loader compiler: VC6
Loader version: 4.0r7
File size is: 475136 bytes.
MD5 sum is: a82aa4dc4ce18ff62ea8faaca97a31be
Loader file: Download loader file
Loader found in ini file: Yes
OS extra security: None
PHPRC is: EMPTY
INI DIR is: EMPTY
Additional INI files: (none)
Server type is: LOCAL
PHP uname: Windows NT EASYSOFT 6.1 build 7600
Server word size is: 32
Disabled functions: EMPTY
Writeable loader locations: C:\inetpub\vhosts\E-touch.ir\httpdocs,
C:\inetpub\vhosts\E-touch.ir\cgi-bin
Find Solve
I do upgrade Plesk and running php in command line mode
php -c "C:\Program Files (x86)\Parallels\Plesk\Additional\PleskPHP5\php.ini" -v
I using the cammand found Problem in php.ini.
When the problem was resolved. ioncube was Run. :D