I believe I have found a bug in Sharepoint 2010, and would like to submit this to the product development team.
I tried to use Microsoft Connect, but it seems that Sharepoint 2010 is not in the active list of products that are receiving Feedback.
Does this mean that the bug reporting stage for MOSS (Microsoft Office Sharepoint Server) 2010 is over? And it is no longer possible to submit product bugs?
Is there another channel of general public communication with the product team? I have an MSDN subscription if this helps.
No, it doesnt in directory.
http://connect.microsoft.com/directory/business-software/
There is an entry for Sharepoint Community under Business Software. And they are accepting bugs as well.
Related
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'm trying to establish whether its possible to connect lists to external SQL tables with SharePoint 2013 Foundation.
I know that is possible in the paid versions through Business Connectivity Services. However, most places I look, BCS is shown as not included in Foundation.
The one thing that contradicts this is page here. Whilst admittedly its titled Office 365, it does include a list for On Premise solutions which suggests that BCS External List IS included in SharePoint Foundation. However, the link takes you to a page entitled “Deploy a Business Connectivity Services cloud-only solution in SharePoint 2013”.
If it is possible, then it seems that we will need to setup a Secure Store to holds ID and passwords for external sources.
Has anyone managed to link Lists to external tables in SharePoint 2013 Foundation (it needs to be 2013 as I understand Microsoft withdrew BCS for that release)? Any pointers would be very welcome to stop us going round in circles.
Thanks,
Chris.
If you have visual studio 2012 installed in the SharePoint server, you can create a "SharePoint 2013 - Empty Project", and then in the project, add a new item called "Business Data Connectivity Model".
You can search for many tutorials for "Business Data Connectivity Model", such as the example link below (note the video is about sharepoint 2010, but you can use it for sharepoint 2013):
http://msdn.microsoft.com/en-us/vstudio/ff623022.aspx
This solution will work for SharePoint 2013 Foundation as I have done that myself.
regards Taz
I am looking for a migration tool. We want to upgrade from SharePoint Server 2007 to SharePoint 2010 in a new environment. We need to have functionality to granulary select which content to migrate and eaven select to map to new structure in the new solution.
We want to tag the content migrated.
The migration tools we are considering are AvePoint, Axceler Davinci, Metalogix.
I'm doing migration scenarios for a consultant firm based in Montreal. First of all, I think you have the correct thinking about how you want to get this done. Doing a SharePoint upgrade (database upgrade) usually bring your SharePoint 2007 problems over to SharePoint 2010.
Here's what we usually do :
Define governance for the new SharePoint platform
Define the new Information Architecture
Implement the new Information Architecture (build sites, lists, libraries, etc.)
Migrate the content over
Tools such as Sharegate (www.share-gate.com) can allow you to do some mapping from your old content source over to the new one.
Hopefully, this will help you!
I'm not sure this is the right forum for this, but here goes:
I'm creating a workflow that kicks off when a user submits an InfoPath form to a form library on a Sharepoint 2007 platform. The workflow should find the manager of the user that submitted the form from SQL and email that person for approval before the next step is run. Is this possible in Sharepoint 2007 or is using SQL in a workflow only a feature of Sharepoint 2010?
Thanks in advance
Try this:
http://sharepointdiva.wordpress.com/2009/03/10/using-sql-inside-workflow/
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.