Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
Ok first of all what is the difference between these two products?
Secondly are the development skills interchangeable between Server 2010 and Foundation 2010?
And lastly in terms of job market, when HR department writes "Looking for Sharepoint developer" do they mean developer for Sharepoint Server (MOSS) or Sharepoint Foundation (Services)?
Note: Working with SP Foundation would be better in my case because Sharepoint Server 2010 brings my computer to its knees with only 3GB RAM. Sharepoint Foundation is it a good starting point or would you suggest going with Sharepoint Server?
Strictly speaking, SharePoint Server IS SharePoint Foundation with additional features. Therefore, all your SharePoint Foundation development skills can be used in SharePoint Server as well. What you should/could use depends on the requirements of your project. Some projects require features that are only available in SharePoint Server, so that narrows your options.
If your PC is not powerfull enough to run SharePoint Server, there's always the option to install it on a development server and connect to it remotely. That is... if you have a development server available.
Side note: the term MOSS is only used for SharePoint Server 2007. Microsoft decided to change the name of the product from Microsoft Office SharePoint Server to Microsoft SharePoint Server.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 4 years ago.
Improve this question
Can we do web automation without using selenium/ QTP etc? I think "No", but just to clarify the answer with proper explanation.
For your question, yes we can automate the web application without using selenium/QTP. Nowadays, there are lot of tools available in the market which can automate the web application. Some of them are mentioned below.
Katalon Studio. Katalon Studio is a powerful automation tool set for web and mobile app testing. It is a free yet feature-packed solution that can be applied to overcome common challenges such as wait-time, pop-up and iframe in web UI test automation. Reference: https://www.katalon.com/katalon-studio/
Sahi is an automation and testing tool for web applications coming in an open-source.Sahi Open-source is written in Java and JavaScript and hosted on SourceForge since October 2005. It is released under an Apache License 2.0 Open Source License and its current version is 5.1 (published on October 5, 2016). Sahi Pro is currently in version 6.3.2 and is hosted on the Sahi Pro Website.
Reference: http://sahipro.com
Ghost Inspector is an automated UI testing and monitoring tool. It allows you to record yourself performing actions on your website within your browser, then sync them to the Ghost Inspector service and run them continuously as a regression test. Reference: https://ghostinspector.com
and there are many more. Please let me know if there are any issues.
Thanks,
Krishna
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
Our company is planning to upgrade Office 2007 to Office 2016. We have worksheets that uses macros. Is it going to be an issues that anyone know of when they have transition from earlier version to Office 2016?
Googling "ms office vba compatibility 2007 2010 2016" yields some helpful results:
M$ has some telemetry information published in Compatibility issues in Office. It's primarily UI controls and components that are dropped from later versions
At M$ forums, someone asking the same question is being pointed to the same link that #Ralph gave
Users mention issues with API calls in VBA compatibility issues: Excel 2007, 2010, 2013 (although that's not the OP's problem apparently)
If you're upgrading your business environment, you'll be testing it out anyway prior to mass deployment - at least, all the common use cases.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I want to configure and install different softwares for a custom CRM solution.
What I need:
· TFS Server 2012 – Solution -
· CRM Dynamics 2011 – Integration with TFS and SharePoint.
· SharePoint 2013 – Integration
· Office 2010 Standard integration
I want to know the installation hierarchy mean first I should install tfs server then sharepoint and so on or first sharepoint then tfs..
Please let me know order in which I should install all these products. Also let me know if any of these products conflicts each other and I have separate db server, mean sharepoint front server will be separate and db server will be separate. I one Windows server 2008 R2 server and other server with sql server 2008R2
That all should work just fine, and all products can share a single database server. For installation order, I recommend:
CRM 2011 Server.
CRM 2011 Email Router.
CRM 2011 SSRS Extensions.
SharePoint 2013.
CRM/SharePoint integration.
Office 2010 and CRM Outlook Addin on client machines.
Verify basic functionality after each step, of course.
TFS doesn't directly relate to the functionality of CRM, and there is no direct integration between the CRM server and TFS. Your developers will want to install the CRM Toolkit and then just connect and use TFS as normal.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
Does CRM 2011 have cross browser support? Or does it still require Internet Explorer?
Edit 04/02/2013. Cross browser support begins with CRM 2011 Update Rollup 12. The browsers supported are listed at: http://support.microsoft.com/kb/2784954
See http://support.microsoft.com/kb/2669061 to see support by product (CRM 4/CRM 2011) and rollup.
Sadly, no other browser than IE is supported for the full webclient (yet). See the Microsoft Dynamics CRM Web client software requirements.
However the mobile front-end "Mobile Express" which is part of Dynamics CRM 2011 is accessible with other browsers. Simply append /mto your url, for example https://crm.foobar.org/m
Still need IE, however you can use IE9 (which does legacy support).
Or can do what I do, use Chrome, but use the IETab plugin (which mocks IE). Then I don't have to have 100 thousand CRM windows open.
Cross browser support wont happen until HTML 5 is used.
I think this is planned for CRM 2012 or CRM 6.
They mentioned this in the CRM statement of direction which you can read about here
http://crmbusiness.wordpress.com/2011/05/10/crm-statement-of-direction-crm-6-release-date-q2-2012/
I want to obtain some work experience information about sharepoint server.Shall I install trail version of Sharepoint on my machine ?If trail version is allowed ,where is the point do i really need to start?
SharePoint 2007 requires Windows Server, but SharePoint 2010 can be installed on Windows Vista and 7.
In my opinion, these 2 books are excellent as starting point:
Inside WSS
Inside MOSS
You can use the free version of Sharepoint. This is Windows SharePoint Services 2007 or SharePoint Foundation 2010. If you are new to SharePoint then you would be better off using the new 2010 version. This is still in beta but should be released really soon.
As pointed out by Timores, you can install this on Win 7 or Vista but if you plan to do development for customers then you should use a server platform like 2008 R2.
Assuming you are a complete newbie to SharePoint, you should spend quite a lot of time learning the platform and architecture. There are many great books and web sites you can refer to.
After that, the sky is the limit. It really depends what you want to do with the platform.
MOSS 2007 / SharePoint Enterprise 2010 is a very large, very complex beast. If you feel happy/bored with WSS/Foundation then give the full product a try.
For me, it's taken 2 years to feel confident with SharePoint development. I fought the beast for a year but now we have arrived at a comfortable standoff. :)