So, this may sound stupid but I don't really get it. When I visited http://www.themidnightcoders.com and download WebOrb for .NET. After I finished product setup progress, I realize that the product that I just downloaded and setup in my machine was "Enterprise Edition in Development mode"
Because when I go into the product web console page. It tell me that, it's in development mode and limit for on 5 IP Addresses. When I return to download-page of WebOrb site I only found one product for download and it's the one that I just downloaded.
So I want to use WebOrb for .NET Community Edition but I have not found it yet.
May you please tell me the solution of this problem?
Thank you
http://www.themidnightcoders.com/products/weborb-for-net/faqs.html
Where can I find Community Edition?
Please contact sales at 1-888-MYWEBORB or sales#themidnightcoders.com to get a free WebORB Community Edition license. (Only one per company.)
You can find WebORB Community Edition on the product editions page for both WebORB for .NET and WebORB for Java. Here is a link to the request form:
http://www.themidnightcoders.com/community-edition-application.html
Related
ee-patch-3.9.5-20211223-DECEMBER-2021.zip on their forums but link says invalid, can someone help me to get that patch to my mule?
Only MuleSoft customers that paid for the enterprise edition have access to patches. If you are a customer you can to login to https://help.mulesoft.com and download available files from there.
I have one small doubt regarding Microsoft.Xrm.SDK.dll. Recently I received an email from Microsoft saying they are turning off support for any Microsoft.Xrm.Sdk.dll version less than 8.2.
I am using Dynamics CRM 2016 (App version: 8.1.1.1183, DB Version: 8.1.1.1183), and SDK client to connect to this CRM. This SDK client uses Microsoft.Xrm.Sdk.dll v6.1.
I want to know will it continue to work or do I have to make change in the code and upgrade the dll?
Thanks
This is probably related to ACS deprecation (which is only applicable for online orgs):
See: https://blogs.msdn.microsoft.com/crm/2017/05/29/update-dynamics-crm-client-sdk-version-to-avoid-calls-to-acs/
With the deprecation of Azure Access Control Service (ACS), you should
modify the SDK authentication code by removing all references to ACS.
Effective from Microsoft Dynamics CRM Online 2016 Update 1 (v8.1.1)
and Microsoft Dynamics 365 (v8.2), we removed Live ID support and ACS
dependencies on the server-side. It is required to update the
references in all client side components by updating the SDK.
For custom applications you need to make sure you have the correct version of the SDK.
Custom Application(s) – If you have developed a Web/Windows/Console
application that is interacting with Dynamics CRM
Scan the folders on your server where the solution is running and look for: Microsoft.XRM.SDK.dll. If found, use the table given in the
Team Blog site to determine which version of the SDK you need to
download.
Using the table, determine which version of .NET that you have deployed against, and confirm the version of Dynamics 365 CRM service
you are using. If you are uncertain which .NET version your solution
is using, contact your development or engineering teams.
Once you have determined the correct SDK version to use simply replace the Microsoft.XRM.SDK.dll found in /bin folder with the latest
version of the SDK dll.Replace Microsoft.XRM.SDK.dll with latest
version of SDK dll
I recommend you to go through the MSDN blog
Without knowing when & where (which CRM version your) project started & staying in 2016 now and what’s your future project plans (whether sustenance mode or stay current), could not comment on action.
As a general practice, do a pilot with an upgrade in separate copy/sandbox & see. Then plan for code Update & sdk upgrade in Live.
I need to install weblogic 9.2 to test a particular web application. Dont find the installer in oracles edelivery or any other site. Please advise
As of December 4, 2012, the BEA Release Archive has been decommissioned. Customers looking for a BEA release that is not available on the Oracle Software Delivery Cloud, or OTN, please refer to MOS Document 1071023.1 'Requesting Physical Shipment or Download URL for Software Media'.
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=464049562271256&id=763603.1&_afrWindowMode=0&_adf.ctrl-state=h3iccxrvr_4
I have developed an extension to Magento Community edition.
I would like to test it on the Enterprise edition.
How can I do that?
Do you think there will be changes between those versions code-wise?
Thanks
I use EE daily. All the differences I can detect are in the form of extra modules in "app/code/core/Enterprise", class names start with "Enterprise" instead of "Mage", some are encoded with ionCube. There is an "enterprise" theme too but it is very similar to "modern". The rest of Magento is the same as the Community Edition so your extension will likely work on both equally.
However you cannot claim compatibility without testing it, that would be irresponsible. It is possible you have overridden something which is then later re-overridden by the other edition. You probably don't want to buy a years licence just for that so you'll have to ask for volunteers, the best places are Magento's forum and chat. Failing that you could advertise on one of the many freelance programmer sites for someone who is in a position to help, that will be cheaper than a whole copy of EE.
Lastly there is the issue of registering on Magento Connect. So far only aheadWorks have the privilege of appearing in the "Enterprise Ed." section. (The "Professional Ed." section isn't even active yet.) You may not get a chance to list your extension there although you can always explain the salient parts on your own website.
Magento Enterprise edition differs from Community edition by following items:
1) There are additional modules, that complement Mage modules. They all have Enterprise namespace (Enterprise_ prefix instead of Mage_ prefix). Enterprise modules either add some new functionality, or modifiy behaviour of Mage modules.
2) Enterprise has its own design scheme. About 30% of templates are overriden, others fall back to base/default theme
3) Enterprise has different license
So, reviewing mentioned above, you cannot guarantee stable work of your CE extension without testing it on EE. It's very probable that your module will fork fine, but I'd estimate a 10% probability that your extension requires some fixes to work normally with EE.
Strictly speaking, you can test your extension only having your own Magento EE ($10 000+).
However there's the other way. Magento EE license allows the buyer to give access to his Magento EE version to people, that are developing some functionality for buyer's Magento. So you can sell your extension to someone having Magento EE, notifying him, that it was not tested on EE and you need to do it. Your client will give you access to his Magento EE and you'll be able to test and debug the extension. That conforms Magento EE license, because you'll be a hired developer for Magento EE owner and you'll be developing extension for his Magento EE.
Of course you should notice that your account at Magento Connect must have special access to posting EE-extensions - usual account can not do this. You need to ask Magento support how to get such privilege.
From my own opinion I recommend do not bother with EE functionality, as it's not easy to perform whole process of testing and posting it as EE extension. CE market is wider (although not so money-full), so you can sell it here.
I agree with clockworkgeek that you are likely not to have any problems, but also that there are overrides in Magento EE that you need to be aware of. Please do find an EE installation to check on, as there may be changes.
I have developed a magento module. It works fine for community edition and enterprise edition in my local environment. After installed it in the live site it works fine for community edition, but not for enterprise edition. It is not showing any admin configuration in enterprise edition. Am I missing anything?
I created an application in vb.net using visual studio 2010. I want to create an installation file of the application that will not be free with a license so I want to create a trial of 30 jours.if there a way I thank you in advance
3rd Party Option:-
If you are open to 3rd party options, you can check out Crypto Licensing for .NET
Building your own:-
The MSDN - VB Developers Center also has a Shareware Application Starter Kit
You can download this and check this out. This should give you some starting points as well as to how to go about it.
There is also an old channel 9 video of how to use it
Caveat : This seems to be a bit old but it should give you pointers to get you started atleast.