I want to use the Web Platform Installer to perform installations and manage dependencies, but because we store version information in a database, the options for discovery that are supported by the WPI won't work for us.
Based on what I've learned so far setting up a custom feed, I don't even know how you would inject any sort of custom logic into the application, but I thought I'd better throw a question out here before I give up.
Is it possible to add custom logic for how the Web Platform Installer discovers which services have been installed?
Thanks!
As far as I've been able to tell, this is not possible. We ended up coming up with a custom solution to fit our needs.
For those interested, chocolatey (http://nuget.org/List/Packages/chocolatey) is another great utility for custom installations.
Related
I'd like to get some business apps up and running quickly with the use of JHipster, which seems like a solid approach; assuming it is allowed. Is the commercial use of a generated JHipster application allowed and if so, what are the proper steps to take in in order to not infringe upon any terms and conditions of open source?
I apologize if this has been asked previously.
I really just need to know how I can go about using an instance of a generated application for something other than an open-source project.
Sincerely,
Art
There are many closed source applications originally generated by JHipster. The generated project is fully yours.
I'm trying to build my first app on Hybris, but I'm not sure what is the best approach to build such applications. Let's say I sell flowers in my store. Currently there are 2 ways how to do it:
Create accelerator template and then reconfigure application.
Building app from the beginning.
The first solution may look very attractive, but I don't think it is better solution because:
Hybris doesn't provide an accelerator for my specific solution (flowers), application reconfiguration may take a lot of time.
Some accelerators contain more that one store - other stores should be removed.
The mess in the database. I have to spend time and understand which tables should be removed.
The second approach seems the most logical, but in this case I have some doubts, because the speed of development will be significantly reduced. Moreover, I think that developing a simple store on Spring Boot will be much faster than learning the Hybris platform's extensions and how they work together.
In this case, how should I start develop my application?
Honestly, I don't have experience with building complete SAP Hybris application from the scratch yet, but I have some experience related to development of the SAP Hybris extensions, so I'll try to provide my potential approach because I don't see many answers here.
I'd do it as follows:
Get the whole commerce suite
Run one of the recipe with the installer script (choose one, which will be the best for you - one of the most popular/common recipes is b2c_acc)
Remove unwanted extensions from the localextensions.xml file if necessary
Add another extensions, if you need them
Depending on your use case, create your own extension basing on the one of templates with ant extgen task inside the hybris/bin/platform/ dir (e.g. yacceleratorstorefront, ybackoffice, yempty, etc.)
Add your custom extension (or extensions) to localextensions.xml file
Start your development within your custom extension created out of available template
I know, it's kind of "specific" platform. I hope this answer will help a bit.
Cheers
I have in my company many MSI installers that I want to unified them into a single MSI.
I understand Suite/Advanced UI project may fit that requirement.
I created a project, added 2 different packages and assign them features.
I want to view the features that each MSI has, maybe load it's dialog to the Suite project but I can't find a way to do that but only built a new dialog which will save properties and pass them to the sub MSI's.
If that is the only then what is the purpose of Suite project, I cant do that in a standard MSI or some C# code to run all my MSI's
Am I wrong?
There are multiple pieces to this question, so I'm going to answer them at a high level. That should help you figure out what you want more detail on so you can ask it in a new question.
It's possible to associate Suite/Advanced UI features with MSI features, but I don't really recommend it. There are a lot of caveats to the approach in that blog post. We've found that it typically works better to design your MSIs to be feature-level items, so that the entirety of any given MSI that is part of a Suite is either installed or skipped.
You are correct that is is not possible to dynamically explore the features of the MSI package. You can create pages with controls that reference Suite properties or features, but you're still back to the caveats of the above post.
The Suite/Advanced UI project is designed to unify the UI experience of installing multiple packages, whether carried locally or downloaded on demand. If they are all MSI packages, and you are willing to require Windows Installer 4.5, it can install them using transaction processing. You are absolutely correct that you could write your own bootstrap to do this, or to just script installing several MSI packages in a row, but doing so requires the usual trade-offs. (It may give a better fit, but it will likely take a lot more work if you want to replicate all the features already provided.)
I have an extension that I'd like users to install along with my app. The app's purpose is very simple: use raw sockets to interact with a remote service and pass some messages to the extension. As far as I know, raw sockets are not available to extensions.
I'd like to avoid forcing users to install two separate packages from the Chrome Web Store. Is there a way to package both into one unit?
If not, what would be the recommended practice in this case?
The target platform is Chromebook/Chrome OS.
Thanks.
I don't think this is possible, otherwise there would be no reason to have both (apps and extensions).
But you can encourage your users to install extension from your app and vice versa.
And you can send messages between extensions and apps so you can ping to check if it is installed or use management permission to check.
It's impossible, each extension or apps has an unique extension_id.
and has single manifest.
But I think it is pretty good idea :)
I think it should be supported from webstore side.
What is the exact difference between p4.net and p4api.net?
I was trying to create a custom gui based tool for perforce and I started developing it using p4api.net. Much later I came to know about the existence of p4.net. Now I am confused with their difference and the purpose.
Also I have a doubt on which option to choose for the development.
Is there something else other than these two?
P4API.NET is the supported API for .NET applications, so I'd go with that. You can see a list of the officially released APIs for the various languages here.