Provide .Net 4.0 Framework support for SharePoint 2010 so that .Net Framework v. 4.0 projects can be built and deployed to SharePoint 2010. In addition, a new/updated set of Visual Studio project templates should be introduced with the newest .Net Framework v.4.0 support.

Integrate SharePoint Designer functionality into Visual Studio so that developers can accomplish all required SharePoint development and administration tasks in a single IDE rather than having to bounce back and forth between Visual Studio and SharePoint Designer for various tasks and development activities.

Connecting to a remote Sharepoint farm exports for projects and items

Provide .Net 4.5 Framework support for SharePoint 15/2013 so that developers can leverage the new built-in Windows Iden***y Foundation capabilities (WIF) that ships with the .Net 4.5 Base Cl*** Library. This will significantly simplify Claims-based development in SharePoint 15/2013 vs. continuing to use .Net 4.0 with limited support for WIF.

Provide native SAML 2.0 support for SharePoint rather than the current support for SAML v. 1.1 in SharePoint 2010.

While I absolutely love the new VS 2012 projects for SharePoint List and Content Types (great job!), we still have to manually enter columns via XML. This is very tedious.... Seems like it would be easy to have a drop down box that lists the OTB columns (single line of text, number, dropdown, date, etc.) and upon selection, the column type XML would be generated - then we would only have to do minor tweaks to the XML. You have dropdowns for the list and content type, please add for columns.

There is no chance to build a backstage extension, because Office Tools contains Ribbon schema from Office 2010. However the UI was changed in Office 2013 Preview.

Previously discussed here: http://social.msdn.microsoft.com/Forums/da-DK/officedevpreview/thread/527ed1f8-b2fd-46d7-8e59-b86089f3e6cd

Provide a generic full-trust proxy for external web services that can be used to call external web services from within sandboxed solutions. This full-trust proxy code should be able to support Classic .asmx services, WCF SOAP Services as well as WCF RESTful/WCF Data Services. This will remove the need to create full-trust proxies on a project-by-project basis for many development teams.

Currently features such as open in DataSheet view are restricted to capabilities only available through Internet Explorer. This reduces the full browser-based experience for users utilizing alternative browsers such as Firefox and Google Chrome. Therefore, all ActiveX dependencies or any such dependencies which require Internet Explorer support exclusively should be removed altogether and replaced with .Net control counterparts or other suitable solutions.

When working with lots of modules, pages, mapped folders, features, ... it can be quite hard to find that one list instance in a list of over 50 items, without being able to search it, nor being alphabetically.

Provide .Net 4.0 Framework support for SharePoint 2010 so that .Net Framework v. 4.0 projects can be built and deployed to SharePoint 2010.
In addition, a new/updated set of Visual Studio project templates should be introduced with the newest .Net Framework v.4.0 support.

Now that SQL 2012 RTM has been released, SharePoint 2010 Hardware and Software Requirements should immediately be updated to provide official support for SQL Server 2012.

I really like the new publishing options for web applications. As for SharePoint, the Package option seems to have been replaced by a Publish option. But that publish option could use some of the features the web application publishing has. For instance choosing a profile debug/release. It also doesn't rememeber the last directory where you've published your file in between session, so I need to choose the folder again each time. Overall, the publish feature is nice, but could be nicer.

While I absolutely love the new VS 2012 projects for SharePoint List and Content Types (great job!), we still have to manually enter columns via XML. This is very tedious.... Seems like it would be easy to have a drop down box that lists the OTB columns (single line of text, number, dropdown, date, etc.) and upon selection, the column type XML would be generated - then we would only have to do minor tweaks to the XML. You have dropdowns for the list and content type, please add for columns.

Provide the ability to version file attachments when they are directly attached to SharePoint List Items. Currently, you can only enable versioning on Document Libraries, however, if you attach a file to a SharePoint List, there is no option to version the files that are attached to these various list items.

It`s impossible to isolate unit test code from SharePoint object model using mocks and stubs for now. To create unit tests developer must use SharePoint emulation or shim based isolation framework. Moreover such unit testing code looks unnatural and bad designed.

Provide Google and Open ID authentication support for logging into SharePoint Portals (both internally hosted SharePoint as well as SharePoint Online)

Office continues to use the dead language VBA for macros. Using the Roslyn project, it should be easier to allow C# to be written directly within Office. This would be a huge, huge improvement over having to write and maintain VBA macros.

VSTO and VSTA are a clunky solution at best, and deployment of Office apps using them is always an issue. Making Office natively support C# is the solution.