I'm looking at taking a possible contract role as an MS Dynamics developer. In the interim, I'd like to play around with x++. Am I right in thinking that the only code editor available is the one that ships with AX?
I'd really like a freebie alternative to use for now, but I haven't come across one.
Not sure that you can get something for free, but you can create a dynamics ax instance accessible from the web, with microsoft lifecycle services.
https://lcs.dynamics.com/
you can also ask your new Company to download a demo VM for you. It's available on the Customer and on the Partner Source.
https://mbs.microsoft.com/customersource/northamerica/AX/downloads/service-packs/AX2012DemoToolsMaterials
Unfortunately, besides MorphX, the native IDE in MS Dynamics, and Visual Studio(for C# dev), you don't have much of a choice.
However, there a portal called 365 Talent portal, where you can register as a freelance MS Dynamics Developer and request for an access to the Dynamics Learning Portal (DLP).
Finally , after your access to the DLP is granted, you can play around with some VMs(with AX installed), read documentation, etc.
Related
I'm not sure if this is the right place to ask this question. If not, please direct me to the right place.
We used to have an application that was created using VB and Microsoft Access. It was an application to score calls from Agents and would then run a few calculations and grade those agents based on a few algorithms.
We replicated all that Access data onto SQL but for some reason, we were just not able to connect the VB application to the SQL Database instead. The application was also outdated and we needed a change.
Can anyone suggest software/framework that can be used to create a new application with an ability to connect to a SQL database?
EDIT: We have a Microsoft Office 365 subscription. I was thinking of using PowerApps. I've never used it before. Does anyone think this could help serve my purpose?
I have extensive experience of using PowerApps to create applications connected to SQL Server (in my case Azure SQL Database), and am mostly satisfied.
There are some constraints, but not major. Please see these posts for some further information.
I would suggest PowerApps if you have Office365.
I had a genius idea today to try and create a website that would access our CRM database and will report on support cases.
The idea would be to have a page that would be visible in the office and members of the support team can view the current status of support cases.
I've downloaded the CRM SDK and I've read a couple of manuals, but I can't seem to find a decent starting point for a complete rookie..
Are there are good tutorials out there on how to create a website that will communicate with CRM's database, preferrably for a VB.NET application.
There are several products that implement your idea.
The most famous one is the Adxstudio, you can find a community edition (also for CRM 4.0) at this address:
http://community.adxstudio.com/products/adxstudio-portals/
After you can check the source code, but they use C#
I am enrolled in masters program and currently I am learning WCF services, their deployment and Microsoft Azure. I am working on an idea which I am hoping I will be able to pull in next 4-5 months.
I am hoping, if I could publish applications like powerpoint and excel or may be their basic functions on a Cloud via Azure so anyone can use those features without even having those applications on their machines over the web(only available to authorized personnel) .
I want to ask how viable above approach could be because it is still a very young Idea. And, It would be nice if I get some professional arguments and may be counter arguments.
Thanks a lot!!
Just use Citrix. They do this already.
Is it possible to use use SharePoint to custom develop a GUI for an SQL Server backend for updating the data? Thanks.
If you are using SharePoint 2007 you might want to take a look at the Business Data Catalogue - http://msdn.microsoft.com/en-us/library/ms563661(v=office.12).aspx
Not sure what the comparable feature (if any) in 2010/2013 is...
EDIT:
In 2013 it is called Business Connectivity Services - http://msdn.microsoft.com/en-us/library/jj163782.aspx#BCSoverview_Whatcanbcsdo
Look at "Business Connectivity Services" and "External List".
SharePoint Designer can make the process pretty simple or you can develop a Visual Studio project:
http://msdn.microsoft.com/en-us/library/ee558778(v=office.14).aspx
If you want to do the legwork try building an Access Application in SharePoint 2013.
It is much better than 2010 but requires more setup. This will encapsulate a database within a SQL database, very versatile super quick and you can do all your SQL fun stuff from there.
This is a low or no code solution.
SharePoint 2010 Access apps use lists as back-end repositories, you can interact with the data in the SharePoint WSS_Content database, but it is not supported and no advisable.
I work for a small digital marketing company as a programmer, and we are not a Microsoft partner or any sort (Gold/Silver/Bronze). However, we use .NET.
What I am confused about is that the developer before me has left, and he gets subscription DVDs of latest Microsoft tools, delivered to the company (Sql Server etc).
I am assumign this is not a personal subscription, because if it was he'd have changed addresses.
Anyway, the subscription is Professional and we use the tools for commercial purposes. Is this allowed? Also, am I allowed to use the tools that we get, at home? I want to use Windows Server at home for dev purposes (learning it for my exams).
Thanks
Thanks for the advice guys.
The license is registered in my boss name but I think a networking guy has added himself as an additional user.
MSDN FAQ says I can have up to 10 instances of the tools installed. I was thinking if I use a product key off MSDN, then that key is forever in use and no additional licenses can be installed.
For the definitive answer read through the MSDN subscription FAQ which includes the license terms.
My understanding is that you can use the software to support development work for your company, but not run production servers. Ie. you could develop Exchange add-ins but not run your company's email using the Exchange Server that comes with MSDN.
Using the software at home is probably a grey area. If it is on company owned equipment and supports your development goals then it sounds OK. If it is on your own equipment then it likely goes against the details of the EULA. You could always try calling Microsoft and asking.
In short, no, you can't use any of the MSDN disks for production services at all. Dev and Test only. If you develop an app using them, then put it into production (eg you develop a timesheet app for yourselves) once it starts being used as a timesheet app, you need to buy full versions of everything it needs.
There's one more thing you need to consider. You need to buy a copy of the MSDN for each developer. Just because it says you can use up to 10 instances does not mean anyone else can (otherwise I could use some of your licences, if you wouldn't mind :) ).
So if there's 3 devs in your team, you need to buy 3 MSDN licences. That also applies if you run a server using the MSDN licence that the other devs access - I think you might be OK if the other devs bought CALs to access it, but the T&C is confusing to say the least.
You also need to bear in mind that MSDN licences are recurring - we bought them on a 3 year select agreement, you might have different terms.
We're being audited by MS at the moment. Turns out developing for Windows can get very expensive :(
Read Microsoft's white paper on Visual Studio 2013 licensing
Example: A developer with an MSDN subscription uses MSDN software at work during the day, but occasionally needs to develop at home as well, using a different computer. Under the MSDN license, there is no difference between a PC at work and a home PC; the home PC is just another device on which the developer is entitled use the MSDN software.
However, the restrictions for the MSDN software running on the developer’s home PC remain the same as in the work environment: the MSDN software installed on the home PC must only be used for design, development and testing purposes; and only other users with an appropriate MSDN subscription can use the software.
Visual Studio and MSDN Licensing White Paper
If the subscription was paid for by the company, you should be able to change the named individual to yourself (or someone else in the company). This would allow you to access MSDN using the subscription to download software and submit problem reports. We had a license that we switched one when one of the licensed individuals left. Unfortunately, our software licensing office took care of it, so I don't know the details of how it was done. We also purchased it under a Select license, so it would probably be different anyway.
Heed #Rob Walker's advice and check out the FAQ for what you can do with the software.