I have been referring to many articles that show comparison between SharePoint Sandboxed Solutions and Farm Solutions plus demos of Visual Web Part (Farm based) and Web Part (Sandboxed Solutions) under Visual Studio 2010 and it seems like Farm Based Development (using Visual Studio) and its deployment is far more preferred way by developers. Correct me if I'm wrong
Moreover,Sandboxed Solutions are restricted that Farm Solutions. Hence in what scenario a developer would preferred to develop/deploy solutions using Sandboxed way?
Sandbox solutions is also depreciated in SP 2013 - so I won't touch them at all.
Please see e.g. http://www.learningsharepoint.com/2012/07/27/what-features-are-removeddepreciated-from-sharepoint-2013/ for more information.
YOu can have more understanding about using the sandboxed solution from the below given link.
https://www.nothingbutsharepoint.com/sites/devwiki/SP2010Dev/Pages/SharePoint%20Sandboxed%20Solutions.aspx
In this link, there is a section for what is supported by Sandboxed solution and what is not supported by it.
Hope this helps.
This far, it has never been possible to me to develop sandboxed solutions because they are too constrained for almost anything. However, if you want to use SharePoint Online (which is a SharePoint environment hosted in a Microsoft cloud), sandboxed solutions are the only way to go.
Related
Visual studio 2013 has its own accessibility validation, to check the accessibility one has to click on the tools menu, then click Check Accessibility, my question is: it is possible to make this validation automatically with MSbuild or with another tool?
Thanks
I need to check websites (MVC projects)
You may also want to look at tenon.io (http://tenon.io/), they have an extension for VS2013.
Tenon differentiates from all the other tools by providing an API which can be leveraged to integrate automated testing in to the development process.
Karl Groves says it better than I could:
All of my projects use Grunt, ... Tenon automatically performs unit testing on its own code. When something goes wrong, Grunt stops and yells at you. You can even tie Grunt to pre-commit hooks. In such a workflow nothing goes live without all your Grunt tasks running successfully.
Imagine, an enterprise-wide tool that can be used in each phase, that works directly as part of your existing workflows and toolsets. Imagine tying such a tool to everything from the very lowest level tasks all the way through to the build and release cycles and publication of content. That’s why I created Tenon.
While Tenon has a web GUI, the web GUI is actually a client application of the real Tenon product. In fact, internally Asa and I refer to and manage Tenon as a series of different things: Tenon Admin, Tenon UI, and Tenon (the API). The real deal, the guts, the muscle of the whole thing is the Tenon API which allows direct command line access to testing your code.
The beauty of Tenon is that because it is essentially an API, it can plug in to anything, Sublime, Webstorm, Netbeans, Notepad (probably not), Visual Studio!
Tenon.io Visual Studio add-on, compatible with 2013/2015 and 2013 Community Edition
http://blogs.msdn.com/b/visualstudio/archive/2015/03/03/improving-html-accessibility-with-visual-studio-extensions.aspx
The only catch, it’s not free for corporate users and it’s in the cloud (unless you pay Enterprise pricing for a local install). Pricing info: http://www.tenon.io/pricing.php
Karl Groves writes about his motivation for creating Tenon: http://www.karlgroves.com/2014/03/13/everything-you-know-about-accessibility-testing-is-wrong-part-4/
I think you need the AccChecker Console
https://msdn.microsoft.com/en-us/library/windows/desktop/jj191809(v=vs.85).aspx
If you want API access to this you should read AccChecker API
https://msdn.microsoft.com/en-us/library/windows/desktop/jj191808(v=vs.85).aspx
Overview here:
UI Accessibility Checker
https://msdn.microsoft.com/en-us/library/windows/desktop/hh920985(v=vs.85).aspx
The closer solution I have found so far regarding this topic is in Visual Studio 2015 by adding the Web Accessibility Checker extension from Mads Kristensen, which is also free. The extension can be found at the Visual Studio Marketplace website. You can see the usage instructions within the description of the extension. This is an example of what you get once build the solution and tap on the Error List panel:
I hope can help.
We have a multi-staged development environment, comprising Development, UAT and Production systems.
When developing solutions that will be migrated across all environments, we would like to be able to take advantage of all of the available development tools, including the SharePoint UI, SharePoint Designer and Visual Studio.
My question is, are the tools mutually exclusive?
Is it possible to create some components like Lists and Views using the UI and Designer, and then use visual Studio to create more complex features like web parts?
If so is there a specific process that you need to follow to make sure all of the tools play with each other for your solution?
In my experience... if it's possible to do in the UI, do it there. If it's not possible to do in the UI, but it can be done in Designer, do it there. If it's not possible in either the UI or Designer, then and only then, should it be done in Visual Studio.
If so is there a specific process that you need to follow to make sure all of the tools play with each other for your solution?
this is a important, but not easy to answer. For instance, I developed a custom web part that stored info in a list. At any point, a site owner could modify or delete the list from the UI and my web part would fail... to this day that's the way it is. It's a classic content management system conundrum, allow users to do their job while prohibiting them from breaking stuff. good luck!
I have searched on Google for this, but have had no luck.
I currently have the enterprise edition of VS2012 (paid by my company). If/when I leave the company I assume I will also lose the license and may have to return to the Express version.
I assume the answer is no, but, will there be any problem loading any of projects in a 'downgraded' version of VS2012? I assume all I will lose is the features VS enterprise offers but my project will work fine.
As for me, most valuable limitations of Express versions are
no resource editor
no remote debugger
does not supports folders in solutions, but projects from folder will be accessible, they just will be displayed in the root of solution, rather in folder.
Thought, there much more limitations, but you may not afraid, Express will open your solutions.
I have been using Visual Studio Express versions. I used to use the full Pro VS 2005. I can't figure out what I am missing with the Express version. What benefits will I get if I buy the full version of VS?
Here you go. This link is vs2005 specific rather than the more-recent 2008, but that's the version you asked about.
Some highlights:
No Mobile Device support
No Object Test Bench
No Extensions
No built-in source control support (they should really change this)
No remote debugging
No Office Development support
No 64-bit compiler support
No Visual Studio Package support
No profiler
No SQL Server debugging integration
Limited deployment options
This list is actually quite lengthy, but with the notable exception of source control they are mostly things you might be able to do without as a single developer, if you really have to. Even the source control can be handled by a file-system-only tool like Tortoise.
Obviously if you're building something like a smart phone app or VS extension it's a non-starter, so you'll need to evaluate what you're really doing. Some of the other missing features like object test bench or the profiler can be partially replaced by third-party tools.
Here's a link to a downloadable Visual Studio 2008 Product Comparison Guide from Microsoft.
The full version of Visual studio supports some extra features and tools.
One of the big differences is more debugging options (You can specify break conditions for debugging, unlike the express version). That feature alone is probably worth it.
You can also install 3rd party addons to add extra featues.
No Resharper.
also, you can add addins like VisualSVN and Resharper into pro. You can't into express.
Matze might be right - MS needs the money - 5K people layed off today, and only 4.7b profit! :(
Depends on what you do. Look at the product matrix to see what features you gain with higher SKUs. Testing, Smart Devices, etc may or may not be relevant for you.
This really just requires a bit of Googling.
You can view a comparison of the paid versions here and an overview of the Express versions here
Have a look at this:
http://blogshare.members.winisp.net/docs/VisualStudio2008-ProductComparison-v1.02-Revisions.xps
If you are doign any sort of professional development with Visual Studio you should buy the Standard edition at a bare minimum. Without it you will loose Source Control integration which IMHO is vital absolute must no questions asked must have for professional development.
I used VS2003 for a while, and am currently using VS2008 C# Express.
Personally, I miss the ability to set a conditional breakpoint instead of simply breaking when a line is hit, and the Threads window.
Support for code version systems is a feature that is real essential.
And Microsoft needs your money to go on implementing new, hot stuff.
I am developing an Isolated Shell that caters to "designers/special content creators" performing specific tasks, using the Shell. As they operate on files, they need to be able to use TFS for source control. This is mainly due to the fact that Developers will also operate on the same files from TFS but using Visual studio 2008.
After looking and searching I still could not find Team Explorer to be available to Shell.
Asking on MSDN forums, lead me to the answer that "this is not supported yet in the Isolated Shell". Well, then the whole point of giving away a shell is not justified, if you want to use a source control system for your files. The idea is not to recreate everything and develop tool windows etc using the TFS provider API.
The Visual Studio Extensibility book by Keyven Nayyeri has an example, which only goes so far into this problem of adding a sc provider.
Has anyone worked on developing Visual Studio 2008 Isolated Shell applications/environment? Please provide comments, questions - anything that you have to share apart from the following threads, which I've already participated in.
Threads from MSDN forums:
Team Explorer for Isolated Shell
Is it possible to use Team Explorer in VS Shell Isolated?
Thanks for your answer. Yes you are right, we will acquire CALs for users without having to buy them Visual Studio, that's the direction we will be taking.
But I am yet to figure out how to make Team Explorer available to such users, inside Shell. So I am looking to find out the technical details of how that can be done.
I mean, I have a user, he installs my VS Shell application, he has no VStudio Team system on his machine. Now if I acquire CAL for TFS and install Team Explorer, do you think it will be automatically available in the VS Shell app?
Any ideas? have you worked on making this happen?
Thanks
It sounds like you are trying to allow the "special content creators" save files in TFS Source Control without having to buy them a license to a Visual Studio Team Edition -- correct me if I'm wrong.
If that's the case, unfortunately I believe that you can't quite do that. Your users still need a Client Access License ("CAL") to access TFS.
I think that you can acquire just CALs for your users without having to buy Visual Studio for them (I presume for less than a full blown Visual Studio would cost). At that point, you can just distribute to them the Team Explorer, which is a VS shell with nothing but TFS access components. That is available in your TFS server media.
I found this via Google. You might want to review it to decide your best options:
Visual Studio Team System 2008 Licensing White Paper
The only exception to the CAL rules I'm aware of is access to Work Items. Assuming properly licensed servers, anyone in your organization can create new Work Items or view and update existing ones created by them, using the Work Item Web Access component.
Just stumbled on this question, it might still be relevant to you.
You have the option of including the AnkhSVN (http://ankhsvn.open.collab.net/) packages and load it into your Isolated Shell. While there are some issues around it, with Subversion support, you could use SvnBridge to access TFS repositories. This might bring you a little bit closer to the process you are trying to achieve.