Is it legal to distribute the Microsoft logparser binary (dll) with my application?
Please check C:\Program Files (x86)\Log Parser 2.2\EULA.rtf for END-USER LICENSE AGREEMENT FOR MICROSOFT SOFTWARE: LOG PARSER TOOL.
I think you should not distribute the binary (dll) within your application. You can tell user to install LogParser before installing your software.
Related
Windows will always tag as unsafe. Written in C+ Visual Studio 6.
Can someone please outline steps to whitelist or digitally certify an exe packed in MSI. I have read that you can digitally sign in later versions of Visual Studio. This is written is VS 6. This is not managed code - their is no layer between the software and low level access. Is their a list for Microsoft to test the software as well as other virus vendors?
If we Installed Redgate tool "Schema Compare of Oracle" on a shared location, Can we access "SCO.exe" Command line from a different Machine or Network? If Yes, Can we run multiple instances at the same time?
If we have more than on Developer than how many licenses we required?
Redgate tool License is Machine specifics or Login specifics?
Redgate licensing is per-user. More information is available on the documentation site.
If the use is as part of a server automated process, such as CI or automated release, each user contributing database changes will need a Deployment Suite for Oracle license. If the use of the sco.exe command line is not a server automated process (eg, running on a desktop), one Schema Compare for Oracle license is required for each distinct user. Per-user licensing allows a user to install the tools on as many machines as they need, provided the named user is using the tool.
I'm assessing moving from TeamCity to VSTS and there are two steps I have in my pipeline that I'm not sure how to setup in VSTS.
How do I include 3rd party dlls in my build? Currently we use a tool that must be installed in the Developer's computers that has separate dlls for x86 and x64. The x86 are included in the project and are needed for the designer, but the x64 are copied from the Program Files folder with an after-build command in Visual Studio. For it to work in TeamCity the tool was installed in the server, so the same after-build command copies the dlls into the build directory as in any other developer computer.
I don't see a way to achieve this in VSTS without including the x64
dlls in the source code, which isn't desirable due to the tool's
license.
How do I publish to SVN? Currently our binaries are hosted in an SVN server. In TeamCity I have a PowerShell script that (in short) updates the SVN local repo in the server, copies all the files from the build directory into the SVN repo and commits the changes.
Storing your dependencies
Lot's of options available here:
Put them in a NuGet package and store them in VSTS Package Management. Have your build restore the package during build.
Put them in Source control, either SVN or TFVC and fetch them during the build.
Store them in Azure Blob storage and fetch them on-demand by downloading them at the start of your build.
Use a custom build agent (Azure VM?) and install the software and the VSTS build agent onto it.
Store them as Build Artefacts in one Build Definition and fetch them using the Fetch Build Artefacts task, which is available from the marketplace.
I'm not sure what kind of license issues you're facing, but I'd expect that each has the same issues if you're not allowed to put the binaries anywhere other than on a licensed machine. Maybe the vendor offers a better option or can be persuaded to offer a Cloud/VM license option.
Publish to SVN
I don't see why the same PowerShell script couldn't be used. Though I'd recommend not to alter your repository from the build pipeline. It makes future CI/CD scenarios much harder. You can attach the binaries as Artefacts to VSTS Builds and that way they can also easily be linked to Release pipelines. You may need to fetch the latest version of svn and store it somewhere in order to run your script. When running on a Azure VM, you can simply install SubVersion directly to the agent.
There is no built-in task available.
I am new to oracle database products. I am planning to install oracle 11g express edition in my PC,it looks like a standard installer.But in many of the oracle database installation tutorial mentions oracle universal installer.oracle universal installer provides more open options,but those options and features not available in downloaded oracle 11g express edition.
difference between two https://docs.oracle.com/cd/E17781_01/install.112/e18803/toc.htm#XEINW151 and http://www.oracle.com/webfolder/technetwork/tutorials/obe/db/11g/r1/prod/install/dbinst/windbinst2.htm
so anyone explain me exactly what is oracle universal installer??Thx in advance.
As the name suggests oracle universal installer is a utility which can be used to install or uninstall multiple oracle products.
The utility can also check pre-requisites before installing a new software.
Only thing you need to do is to provide path to products.xml file inside oraparam.ini file. This can be location for the file on your physical machine or remote location may be hosted on oracle site.
The products.xml file actually have the information about the product being installed for example it is Oracle Client or DB.
For more information please check this link
FYI, this question would have been better asked on the DBA site since it has nothing to do with programming.
XE is a minimal installation for test/dev work so I guess they decided not to clutter it up with OUI, which I have never liked anyway. OUI is simply Oracle's Java-based installer that installs and keeps track of the majority of Oracle software you have installed on your system. There's nothing special about it, and you have no need to worry about missing out on something. If you were installing the standard database, it would try to start the network config tool that creates the TNSNames.ora file, for example. It's been a while since I used XE but I think it's install just creates a generic one for connecting to the XE instance.
I have an application that needs to be delivered as a package.
What are the best among EXE and MSI Installers, and why?
Is there any open source tool to decompile the EXE or MSI?
It depends on what kind of EXE you are talking about.
MSI is setup package that is run by Windows Installer. If you make setup project with Visual Studio it will provide both MSI and EXE for you. EXE in this case just a bootstrapper (MSI or EXE). It will run MSI after checks that Windows Installer is in place.
If you use other tools like InnoSetup, this EXE is a setup package itself, not a bootstrapper.
Regarding to your question about MSI editor: Orca MSI Editor.
If don't need need very complicated installer, I suggest using Visual Studio setup project as it is simple, yet powerful enough.
Many installers these days use MSI internally although they're distributed as EXE. You need an EXE to ensure all the prerequisites are installed: .NET framework, for example; and it installs the prerequisites if they're not. Then it extracts the MSI package which handles the rest of the installation.
MSI provides some advanced install features:
rollback support: if something failed during installation, it returns the system to the state before installation started.
repair: if your application stopped functioning correctly, users can use this feature to reinstall the application. It restores missing files, registry entries.
updates/upgrades: MSI handles application updates/upgrades. MSI package can be configured to automatically the previous version of the application when user starts installation of a newer version. This happens transparently to user: it looks as if only the new version is installed.
patches: MSI supports patches. When only several files of your application are modified, you can update them using a patch package (MSP). The patch will be smaller than the full package.
advertised shortcuts: you can allow users to not install some features of your application unless they're used. When users access such a feature, MSI installs the necessary files.
Though it takes some time to learn the technology.
You can do anything from an EXE file, while MSI is for installation only. Inno Setup and NSIS installation packages are distributed as exe files. They have a scripting language which describes installation steps.
WiX toolset has MSI decompiler called dark.
check Difference between EXE and MSI
I posted a summary of some MSI benefits (and problems) on serverfault.com:
https://serverfault.com/questions/11670/advantages-of-using-msi-files
MSI is a Microsoft Installer, it is newer than the older EXE , Wise Installer and many others support it. It allows for a smarter install with what needs to be deployed (like CAB files, and registry settings etc...) and it can check for previous installs etc..
MSI are ONLY installations, while EXE can do other things like run.
I would use InstallShield and build an MSI
I'm unsure about #2
You can just tell Visual Studio to make your application into an MSI/EXE. If that works and does what you want, just do that. It much effort on your part creating an installer.
MSI means you are using Microsoft's Installer. Microsoft has legitimate reasons for recommending (i.e., not giving your application Certification) MSI. However, a good MSI is tough to produce, so I don't recommend it unless you need your application to be certified.
If you don't require certification, I recommend Inno Setup, along with a front-end like ISTool. It's easy to use and gives you simple interfaces to perform most common installer tasks. In a pinch, it supports scripting to allow you to do anything it doesn't support.