We are planning to procure ABP commercial license for our new project. In the mean time we are planning to do R&D/Learning/Development using ABP opensource code. Once we procured our commercial license. Is it easy to migrate our code from open source free version ABP framework to ABP commercial? Do we face any issues?
ABP Commercial is built on ABP Open-Source Framework, So the answer is both YES and NO.
You don't have to migrate anything, you need to add Commercial features that you need or change the theme as you wish. So, your code once you wrote won't be changed. But you'll able to use commercial modules.
We migrated a simple app from Open Source to Commercial and was easy. We generate all modules again, using abp suite and everything compiles OK.
Related
I've inherited an application, whose origins are lost in the mists of time. It's fairly obvious, based on DLL references and database tables, that the application is based on some edition / variant of ASP.NET Boilerplate. The question is exactly which one? The possibilities (I know of) are:
ASP.NET Boilerplate (free, open source)
ABP Framework (free, open
source)
ASP.NET Zero (licensed, source provided)
ABP Commercial
(licensed, source provided)
Whatever I have, it's obviously an old version since it's running on .NET Framework. (Latest versions of all of these application frameworks run on .NET Core.) We are working toward a phased transition to .NET Framework on .NET Core but one of the first things I picked up on is the incompatibility of my existing database structures for account authentication with the latest ABP Framework. One of the prerequisites for a phased transition is that a single database repository should accommodate account authentication from both the legacy system (as it does today) and the new system we are going to start constructing. I'd like to start working on various alternatives to bridge the gap from "here" to "there" but I'm handicapped by not even knowing where "here" is. I do know that the existing application is based on some variant of ASP.NET Boilerplate, but there are at least four of those. If you can help me pinpoint exactly what I've got, that will be immensely helpful. Thanks!
(All application ABP references are to DLLS. We don't have any ABP source code which might be useful for identification purposes.)
Here is a snapshot of the database tables, if that helps to make the identification:
Here is the one row within the abpEditions table:
Packages with the Abp prefix belong to ASP.NET Boilerplate or ASP.NET Zero. Packages with the Volo.Abp prefix belong to the ABP Framework or ABP Commercial. Since you have the Abp.Zero package, it appears to belong to ASP.NET Zero. The version information also appears to be 4.0.
I have created an .msi installer. I want to further add prerequisites (such as .Net) but when I go to Setup Project properties, the Prerequisites button is disabled. How do I enable it?
Other details:
I'm using VS 2015, SQL Server 2008 R2, .Net 4.5.2, C#, WinForms, Win
10 Pro x64
My setup project is in the same solution as the main project
Prerequisities in Visual Studio Projects
In Configuration at the top of the dialog, did you try to select either Release or Debug? That should enable the Prerequisites... button.
Unecessary, outdated prerequisites?
One pet-peeve of mine: is it really necessary to include the .NET runtime as a prerequisite when most users have it installed by their deployment team (corporations) or via Windows Update (home and small office users)?
If there are security updates for the runtime, your old, embedded runtime is just a nuisance to be honest. Corporate packagers spend a great deal of time removing runtimes and prerequisites for corporate deployment where all runtime components are packaged separately in the corporate standard format. Perhaps consider making a special corporate "large scale deployment" version of your setup bundle? Just a zip with components will be very appreciated, along with a one page PDF on how to deploy them.
For the .NET framework you could just add a launch condition to abort the installation if the runtime is not found, and tell the user to get the runtime via Windows Update or from their system administrator or deployment team.
Just a thought I wanted to share with you. Prerequisites can really bloat a setup - especially when they are almost never needed like the .NET framework. In the future we will certainly pull prerequisite packages straight from online repositories and not embed anything in our main setups (and probably struggle with new security issues from that approach).
What version of the .NET Framework is included in what version of the OS?
Selectively disable versions of the .NET Framework (.NET versions overwrite each other)
WiX and other deployment technologies
Setup projects are rather limited. If you find yourself needing more features, you might want to check out the WiX toolkit.
Here is a previous answer on WiX and other deployment tools that seems to have been helpful for people: MSI vs nuget packages: which are is better for continuous delivery?
I am new to .Net nuke, I want to display the records in Repeater control and do some group by functionality and order by functionality from database(Sql server 2008 R2) and I need to use( .Net Nuke 6.0 & Entity Frame Work 4 or 5), I have to follow MVP, please give me any suggestions, Thanks
If you are looking to use DotNetNuke for your own purposes, you can use Entity Framework without any special considerations.
If you are looking to deploy a commercial solution on DotNetNuke, you will want to consider the use of the {objectQualifier} and {databaseOwner} configuration options. As supporting those is important for widespread DotNetNuke support and not 100% easy to do with EF.
You should consider using PetaPoco over entity framework. DotNetNuke 7.x has PetaPoco support built in and, IMHO, is a much better solution.
Learn More: http://www.charlesnurse.com/Blog/tabid/226/EntryId/56/DAL-2-Caching-Scoping-and-Custom-Mappings.aspx
Is there any way to integrate version control system for Apex & Visualforce code? I can thinking of keeping a separate repository but no way to have it integrated with Salesforce Platform.
Thanks in Advance.
You can do this by using Subversion and the Force.com Eclipse IDE with the Subclipse plugin.
Here are a few links to some instructions.
Setting up Subversion (Windows)
Installing Force.com IDE (Eclipse)
Installing Subclipse (Eclipse plugin)
Use the update site when installing in Eclipse - similar to the instructions here
If instead of using Subversion, you wish to use Git (lots of the community code is hosted on GitHub where you can get it for free) then have a look at this Dreamforce session and some hints and tips about how best to use Git and Force.com together here.
Are there any TFS plugins available for the Force.com IDE? We are trying to centralise our CRM, and we would like to have TFS integration in Force.com IDE.
Which plugins are available? Which have you found most useful.
Does anyone know about this, which plugins are available?
We need this as we already have a historical repository in TFS with respect to the existing application framework. We are likely to add couple of more Force.com utilities to the framework. Hence it would be more mangeable to have a single repository rather having it on multiple ends. Any Idea will be appreciated
Well, force.com IDE is essentially a customized Eclipse so a TFS plugin for eclipse should in theory work, check here.
Though, I am not certain why you need it, SF sandbox itself in combination with Force.com IDE is a form of merge-based Apex source repository.
Just to clarify things first. The Force.com IDE is built as a plugin for the eclipse editor. There are many many other plugins for eclipse. What you want is http://www.teamprise.com/index.html - this however is not free. If you have an MSDN account it should be available to you already.
I use eclipse with the Force.com plugin and the subclipse (subversion) plugin side by side and it works quite well. So I'd assume with a bit of tinkering you can get teamprise working alongside the force.com plugin.