sharepoint workflow solution not working - sharepoint-2010

i have made a sequential workflow in visual studio 2010.
the workflow is working fine on me local machine. i have packaged it to a solution and uploaded it to our intranet. using site settings solution and then add solution and activate it. when i go to site features i don't see me solution and it's not working on the list i have made it for. anyone knows how to fix this ? i'm using sharepoint2010 foundation.
the language i have made it in is english and the site where im trying to install it is Dutch.
thanks in advance.

Check that the workflow is published.
This link may also be of help. There is a slight chance your problem might have to do with localization issues.

Related

How to properly configure application in Live Connect and project in Visual Studio 2013

My question here is pretty simple: how to properly (and 100%) configure both Live Connect and project in Visual Studio 2013 in order for the local application run and authenticate an user properly against Microsoft account.
My question may be simple, but the answer is most likely not as simple. I've been reading countless articles and possible tutorials about this, but they are all fragmented and divided into small parts that do not really conciliate each other.
So below is the situation better described, with the steps I have followed.
[Steps Followed]
1) I have created a simple MVC application using Visual Studio 2013.
2) I have configured the project (using its properties) to use IIS Express with current Project Url : https://localhost:44302/
The project runs quite well, and external authentication with Facebook, Google and Twitter run very well too. Now for the tricky part:
3) I have created account with Microsoft and successfully created application in the Live Connect Developer Center.
4) Since configuring the field Redirect URLs to a simple http://localhost:<port> will not work (well...just because they didn't want it to, I suppose), I have additionally done the following..
5) Mapped in hosts file the following domain to localhost: # 127.0.0.1 mytestdomain.localtest.me
6) Reconfigured in Live Connect the Redirect URLs field to use the newly mapped domain: http://mytestdomain.localtest.me (although I have tried this with or without the port as well).
[End result]
With this configuration, the site runs properly locally. However, when I try to sign in with Microsoft account credentials (so, when I click the "Microsoft" button), I have redirected and received the following message:
"We're unable to complete your request
Microsoft account is experiencing technical problems. Please try again later."
I honestly do not understand why wouldn't this work, when a couple of articles suggested that doing these specific steps would make it work.
What can I be missing, why would this happen at all?
If someone can write here what am I missing and we could all join effort and create in this topic a full fledged, 100% working configuration for local application testing with Microsoft authentication, I believe it would help everyone. If such topic already exist and you can point me to it (because clearly I have missed it) it would also be great.
Thank you in advance,
Mad
Actually I just found out a proper and direct answer to my question. I totally missed it somehow during the last few days of research.
Microsoft's blog has all you need to make it work, and now mine does too. No big explanations and discussions, just basic and direct step by step article.
For those who could not find it and stumbled upon my topic here in StackOverflow, here is the link. Follow it word by word, and it will work.
Answer : Configuring your ASP.NET application for Microsoft OAuth account

Trying to load opserver

I downloaded opserver that I saw at SQLPass. I can't seem to do anything with it. I tried opening it with VS 2008, VS 2010 and keep getting incompatible errors. What version of VS should I be using? I am a newbie so am in real unfamiliar territory. What do I do after I download it? Are there step by step instructions anywhere?
Opserver targets ASP.NET 4.5 for concurrency features, which I believe requires 2012 or better.
The official Opserver documentation assumes that you know how to build and publish and ASP.NET MVC 4 application. Typically the challenge in building MVC is getting the right dependencies/config setup on IIS the first time. Very easy to update after that. There are many blog posts and good answers on this site on that general subject.
If you want directions specific to Opserver, currently you are limited to third party blog posts such as the following:
Patrick Hyatt: Setting Up StackExchange's Opserver (very useful for the config files)
Danny Sorensen: Using Opserver Will It Build? (my own experience so far)
If this is not familiar territory, I recommend the following:
Use Visual Studio 2012 or 2013 on a machine with ASP.NET 4.5
Only enable the Opserver security file. Modify it for your IP address, or use "alladmin" to start.
Build it. If it doesn't work, use StackOverflow to solve your issue. You're having trouble with ASP.NET MVC 4, not Opserver at this point.
Now enable one additional config file at a time and build it again until you are done. Note, that you will not need to enable all of the config files unless your setup matches that of StackOverflow. Most of the config files are intended to be optional and left disabled.
You should be good with 2010, but you need to have ASP.NET MVC installed before opening the solution and building.

How to integrate sharepoint web part?

I am new to SharePoint development.
I have download a '.wsp' file which resides in C:\SlideShow.wsp I want to use this file in my site as web part. I searched over the internet to integrate it and found many solution to do so through power shell script using the command.. Add-SPSolution -LiteralPath but it is not working in my case.
I executed this commannd `Add-SPSolution -LiteralPath "C:\SlideShow.wsp" but it gives error..
How do I integrate it?
Please help.
Go under the Page where you want to add it: Settings->Site Settings->Solutions->Upload Solution
Or with Powershell
Make sure:
Started SharePoint 2010 Manangement Console
Started it as Administrator
For Farm solutions use:
Add-SPSolution C:\SlideShow.wsp
For Sandbox solutions use:
Add-SPUserSolution C:\SlideShow.wsp
As Mark says you have to enable web part from Site collection Features , But it should be automatically enabled , FYI whenever creating a web part in VS2010 please check that you are referencing your web part to SP2010 site other wise SP will not consider it in its trusted zone(Safe Control) , If you are still unable to locate your web part register your DLL in GAC . Sharepoint will consider it as a Safe control .
--Sorry for short answer ,,Please let me know if it works .

Outlook VSTO addin deployment .NET, auto update tool from web aside from ClickOnce?

Hi guys I need to know if there is a tool that I can use to have my outlook addin(assume that it has been successfully installed to many users) get auto updates from a web server? I'm thinking of ClickOnce but I'm not sure of using it since there are drawbacks on its implementation.
Do you have any suggestions? or should I deploy it with ClickOnce?
any of you have an opinion/experience with ClickOnce deployment?
This is an article that describe how to add an automatic update service for an application, give it a look: Adding automatic updates to your program
Updated:
Another interesting approach is the ".NET Application Updater Component" which is the answer of a similar question "Auto-update library for .NET?" where you can find other interesting answers too.

no-touch deployment

I am finding all sorts of general descriptions of no-touch deployment and lots of questions and problems, but I can't figure how to just get started with it. What is the method that makes it happen? I'm working in VB.Net 2005. I think assembly.loadform will suit me best since I know all of my users and will deploy via my intranet.
Appreciate any links or suggestions for starting places (other than googling "no-touch deployment", I already did that).
If it's a web application project that you're deploying, one-click publish with Web Deploy may be what you're looking for. Here's a related link:
How to: Deploy a Web Application Project Using One-Click Publish and Web Deploy