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
Related
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
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.
ON TFS2012 is it possible to request feedback from customers that are utilizing the web client without them having to install feedbackclient.exe on their machines
Usersnap allows customers to add feedback without installing anything locally. It integrates into Microsoft Team Foundation Service (this means, every feedback from your customers is automatically created as ticket inside your TFS workflow).
Your customers even don't need an account in TFS to provide feedback.
It's easy to integrate Usersnap with TFS, you can have a look at the docs here: https://usersnap.com/support/docs/apicfg#tfs
To work with the feedback request like it is explained here it is not possible to give feedback without installing the client tool.
I thought it would work also by logging in in the TFS web interface then open the feedback request and answer to it but apparently after testing it myself I did not found a solution directly. Though the feedback would be filled in completely manually while all the needed tools are available with the client tool.
I am new to SharePoint 2010. What is the main difference between sandbox and farm solution. Can you give me 5 differences to remember. I googled, but there is lot of matter to understand. As a start up guy, i want to know the basic difference.
Thanks for your help.
Farm Solution:
Farm solutions, which are hosted in the IIS worker process (W3WP.exe), run code that can affect the whole farm. When you debug a SharePoint project whose Sandboxed Solution property is set.
Sandbox solution:
Sandboxed solutions, which are hosted in the SharePoint user code solution worker process (SPUCWorkerProcess.exe), run code that can only affect the site collection of the solution. Because sandboxed solutions do not run in the IIS worker process, neither the IIS application pool nor the IIS server must restart. Visual Studio attaches the debugger to the SPUCWorkerProcess process that the SPUserCodeV4 service in SharePoint automatically triggers and controls. It is not necessary for the SPUCWorkerProcess process to recycle to load the latest version of the solution.
For more please refere this link
You can also refere this to know sandbox solutions goodlink
Farm Solutions:
Farm solutions are hosted in the IIS worker process (W3WP.exe).
If you run any code in farm solution the whole farm will got affected.
If you deploy any feature or retract any feature the whole application pool got recycled.
Since they are scoped as farm level, they have full trust access to all the resources.
When the Sand boxed Solution property is set to False, selecting Build\Deploy will deploy the solution to the Farm Solution Gallery.
Sand boxed Solution:
Sand boxed solutions are hosted in the SharePoint user code solution worker process (SPUCWorkerProcess.exe).
try to this link
- The process runs under a CAS policy that restricts programmatic access to any resource outside the sandbox.
- So it never restart the IIS application pool.
- If you run any code it will affect only the site collection of the solution.
- Helpful if you have shared hosting.
- When the Sandboxed Solution property is set to True, selecting Build\Deploy Solution deploys the solution to the site collection Solution Gallery.
One major difference in the deployment is Farm solutions are installed and deployed. Sandboxed solutions are uploaded and activated.
This Link http://www.enjoysharepoint.com/Articles/Details/differences-between-sandboxed-and-farm-solutions-i-66.aspx
Farm solutions, which are hosted in the IIS worker process (W3WP.exe), run code that can affect the whole farm.
Sandboxed solutions, which are hosted in the SharePoint user code solution worker process (SPUCWorkerProcess.exe), run code that can only affect the site collection of the solution.
(from http://msdn.microsoft.com/en-us/library/ee361616.aspx)
One major difference is we can't create Aplication pages in Sandbox solutions.Beacuse Application pages are stored in the 14\TEMPLATES\_LAYOUTS and when we deploy as sandbox we dont have permissions to the physical folder.
Also we cant create VISUAL web parts in Sandbox soultions.
We cant use code to connect to the external web services or to database in the sandbox soltion
Farm solutions are installed and deployed. Sandboxed solutions are uploaded and activated.
Normally we are using Sandbox solution for Online sharepoint such as office365. In this case user will get a solution to work with, but not the Physical system folders. So we cant give any images or contents into the Layout folder(it is restricted). And the main thing is We couldn't able to use some SP-class features in the Sandbox solution(which can be get the information about other farm solutions and server information). Thus farm solution is restricting this SP classes, system folders along with SPUCWorkerProcess process.
We can create the Visual Webparts as Sandbox solutions in 2013 but we have to make sure about the classes and we never want to use the layout folders etc.
Farm Solutions properties:
Farm solutions are hosted in the IIS worker process (W3WP.exe).
If you run any code in farm solution the whole farm will got affected.
If you deploy any feature or retract any feature the whole application pool got recycled.
Since they are scoped as farm level, they have full trust access to all the resources.
When the Sand boxed Solution property is set to False, selecting Build\Deploy will deploy the solution to the Farm Solution Gallery.
One major difference is we can't create Aplication pages in Sandbox solutions.Beacuse Application pages are stored in the 14\TEMPLATES_LAYOUTS and when we deploy as sandbox we dont have permissions to the physical folder.
Also we cant create VISUAL web parts in Sandbox soultions.
We cant use code to connect to the external web services or to database in the sandbox soltion
Farm solutions are installed and deployed. Sandboxed solutions are uploaded and activated.
Farm solutions, which are hosted in the IIS worker process (W3WP.exe), run code that can affect the whole farm.
Sandboxed solutions, which are hosted in the SharePoint user code solution worker process (SPUCWorkerProcess.exe), run code that can only affect the site collection of the solution.
Please look the website that contains more details about the Farm Solutions and Sandbox Solution details :
http://www.techcontents.com/uncategorized/difference-farm-solutions-sandbox-solutions-sharepoint-2010/
I use windows XP and R for my desktop use. And a shared hosting account (at some company) for my web hosting needs.
I wish to create an R web application and I understand that one such way is by using R with Apache through RApache , but since my current shared hosting plan doesn't allow me to install RApache I am a bit stuck.
So... (and here's my question) what would be the easiest/fastest/cost-effective way to get started?
Buying a more expensive hosting package ?
Hosting the thing myself? (on windows ?!)
switch to some other hosting company that permits the use of RApache?
Any suggestion will be most helpful.
Self-hosting is an option if you insist on using RApache. This might be easier than you think. Here's a link to a blog post i read a month ago before i decided to buy the hardware and server my own files. i just watched this seven minute YouTube video tutorial entitled "R Web Application–'Hello World' using RApache" I believe this was just posted today.
In seven minutes, the author walks through building a "hello world" Site using RApache then walks through a more ambitious example, building a user-input form to collect inputs then deliver them to a particular R function--pretty much a exemplary slice of what i suspect most people would want to use RApache for.
A second option is using a web framework. My recommendation here is Django. Why? It's written in Python so you can access R functionality via the python bindings (RPy2). Second, if you are not an experienced web developer, Django is in many ways, a great framework to begin with because it's truly a "full-stack" solution--it works more or less out of the box. In addition, there is a substantial and growing body of quality step-by-setp tutorials, code snippets, and even packaged django Sites, to learn from.
it seems they provide a VMWare image to get up and running quickly.
I suggest you download VMWare player and try the image. Since RApache isn't available for Windows, this is the most simple way, I guess. I wouldn't use that for hosting, but I would first try whether this stack is actually the right thing for your app. Also, this allows you testing things locally.
Doug,
Should I read your suggestion as saying that a Django app can call the RPy2 functionality without RApache? If so, that sounds like a solution for folks on shared hosting who can't install the RAPache module.