which project use to create event receiver for sharepoint 2007 list - sequential workflow or state workflow? i'm using VS 2010
Neither.
Workflows are events which are run via the SharePoint Timer service and can be executed by any server in the farm.
An event receiver is essentially an event handler that will be executed either synchronously or asynchronously (depending on which event you're implementing) on the same server which handled the request that triggered the event receiver.
Visual Studio 2010 does not have much OOTB support for SharePoint 2007. You might consider installing the WSP Builder extensions (note that the proper download is not the recommended download - you'll need the 2010 BETA 1.4). They give new project types which include event receivers. Note though that there are some quirks with those project types but overall they are very helpful to getting the project set up correctly.
Be sure to read the documentation regarding the folder/file layout of your projects. If done correctly, you can use WSPBuilder to generate your WSPs for you.
A quick search revealed this blog post which might help get you started with regard to project structure. I'm sure there are many, many more references available. Happy coding!
Related
I've been exploring UIPath community edition and have come across that the Main window and most of its activities are just like a Visual Studio Workflow. Is it right to say that UIPath is built upon Workflow Foundation of .NET Framework? I'm just trying to reconcile them both in my head now.
Yes that is correct. You can use many functions and methods within UiPath that come from .net. If you press crt+space when you are typing code you will get a list of all functions and methods available. You can even invoke code and execute previously saved Microsoft code.
Not only it's build using Microsoft Workflow Foundation but you could also extend UiPath using Activities build in very similar fashion to WFF. So if you know how to create NativeActivity for example, you already know how to extend UiPath.
Note that the development in UiPath is not really code-extensive, knowledge of .NET is a plus but not mandatory.
How to customise I have knowledge to customise process template in tfs 2015 or in 2012 but for upgrade version in 2017 is there any changes or any enhancement.
I have find in google but I have not found any helpful to customise process template in 2017 specifically.
your help should be appreciated. thanks
The first step is you need to download the process template you want to edit from you TFS server. To do this, launch Visual Studio and navigate in the menus to "Team -> Team Project Collection Settings -> Process Template Manager". When the dialog shows up, you will be able to select the template you wish to edit and download it. Detailed instructions for this can also be found here.
Once you have downloaded the process template, you have a series of XML files that describe how TFS should handle almost everything when you create a new project using that template. The XML can get overwhelming quickly, even for the most seasoned person. You should ideally use the Process Template Editor which is a plugin for Visual Studio (the link is for Visual Studio 2017). For details on customizing a template, you should start off by reading the Customize a process template on the Visual Studio documentation site.
Once you've made your changes, you simply need to upload your process template back to the server using the Process Template Manager (where you downloaded the template). If you replace an existing template, anything using that template will get the updates. If you create a new template, only new projects using that template will be able to make use of it.
Not much has changed with editing the process templates between TFS 2013, TFS 2015 and TFS 2017. So if you find a blog or a write up on one of the versions, there is a good chance it's still valid. There may be slight differences in UI, but there shouldn't be anything ground breaking.
DISCLAIMER!!!
Now that I've answered your question, I would be negligent if I didn't explain the dangers of what you are about to do. Customizing a TFS process template can be very dangerous to your TFS server. Microsoft does not guarantee or put any warranty on changes you make. You customize a template, you are on your own. You have to understand that this template literally tells TFS how to work. It is highly recommended to have a sandbox environment complete separated from your production server and make all changes in said sandbox environment first. Only after you've validated the changes should you move it to your production environment. In addition, anytime you deploy a change to your production server, make sure you have healthy backups your databases. I can't stress this enough.
Lastly, any changes you make, you run the risk of locking yourself into a specific version of TFS or making your upgrade path far more difficult. My last piece of advice is to carefully weigh the need for customization over the risk associated with making it.
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.
Our organisation is using Team Foundation Server. At the moment, developers are manually adding issue tracking references to their check-in comments. We have a custom check-in policy that enforces a valid reference has been added to the comments.
What I'd like to be able to do is provide the user with a user friendly dialog/UI component that allows them to select an issue from a list which will then insert the reference, in the required format, into the comment box.
We are mainly using Visual Studio 2010 but some development still happens on Visual Studio 2008. The issue tracking software is a 3rd party one called OnTime.
Is this possible? Can someone help point me in the right direction.
Doh! It was as simple as creating an instance of a form and calling ShowDialog within the Evaluate method.
Can someone give me a quick explanation of when I would use Visual Studio 2008 Outlook 2007 Ad-In project type? and how would that compare to developing a bunch of outlook macros directly in outlook?
Basically, I want to have some sort of application read email (with attachments) from a pop3 email box, do some filtering/editing/validation of the subject/sender/content and then if certain conditions are met, save the attachments to a local file, and then add an entry into an SQL server database table (i.e. date/sender/subject/message).
Seems there are at least 10 different ways to do this....so between an outlook macro and a VS Office Project, how do I pick?
I am not clear, if I create this solution as a Visual Studio outlook add-in, where does it run? Is it loaded into outlook, does it run as a separate process and communicates back and forth with outlook? if outlook is not running, does it start it?
An Outlook Add-on is a compiled component that uses the Outlook API to perform the tasks you need. A macro/VB script is an interpreted script that actually uses the same API. The add-on approach is better if you want to deploy your functionality.
When you work on an Outlook add-on in Visual Studio, you'll be creating a .NET component, which integrates into the Outlook application, which is written in C++ so uses COM. You'll have to be careful about managed/unmanaged types and releasing objects you retrieve from Outlook.
I have recently completed just such a tool, but I chose to use Add-in Express (http://www.add-in-express.com/). These guys provide a layer of abstraction over the [challenging] Outlook API and also provide some excellent support if you're stuck.
In my case, with Add-in Express, I "run" by setting Outlook as the application command to run, in the Project properties. Add-in Express sorts out the installation of the add-on within Outlook. So when I press "Run", Outlook starts and my add-in is displayed, which may be debugged in the normal fashion. I'm not sure how VSTO (Visual Studio Tools for Office) works in this respect - or at least, I can't remember.
This is an example of an outlook add-in..
Personally, I don't see macros distributable.