Have just jumped on a brand new SharePoint 2013 massive Intranet project and because of specific working conditions have found some items that required addressing almost immediately in order to continue the job. Maybe this will be interesting to someone else who is about to start SharePoint 2013 development to have an idea of what might be necessary. I started working with SharePoint using my own infrastructure in 2009. I used iMac with 320GB HDD and 4GB RAM running VMWare Fusion to virtualise Windows environment ( SQL Server 2008, standalone SharePoint 2007, Visual Studio 2008, Office 2007). It was all-in-one virtual machine. A bit slow, but enough for any SharePoint work that I had at that time. For communication with colleagues and partners we used GoToMeeting . Great tool that worked (and still works) without any problems. Voice, video, screen-sharing - all worked well using built-in audio/video hardware. In 2010 I got a MacBook Pro with 500GB HDD and 8GB ...
We are facing the same issue. We are still facing the same issue even after appending /m to the sharepoint site.
ReplyDeletekindly let us know the solution if the problem is resolved at your end
gayatri, are you talking about mobile view of the SharePoint 2010 Foundation site? if yes then I didn't have a chance to work on any similar issues recently. The resolution I provided in that post worked well for me.
ReplyDelete