I would like to create a timer job that will consolidate some information for reporting purpose in a sandboxed solution, is this doable? please show me the way if yes.
View Complete Post
I am trying to create a test Timer job in SharePoint and want it to be deployed as a solution package. I am using a web application project and added Timerjob.cs, fetaurereceiver.cs, feature.xml and manifest.cml files in in. Then I created a .dff file to
arrange the solution package. But when I tried to create a solution package with makecab.exe i got the below error
100.00% flushing current folder
I dont know what to do with that . Please if anyone can send me an example where a timer job was deployed as a solution package it will be of great help
How could i utilize the sandbox solution to my my SharePoint 2010 development, staging and production environment?
In order word, Could I use sandbox as my SharePoint staging, and development environment? Does the sandbox runs as a separate server from production servers?
Thanks in advance,
Hello, I am working in a aspx web application that must be built in several separate "modules" with different functionality which will be partly developed by different teams.
However, I need the completed app to reside in ONE virtual directory. There will be a single startup page. I need session state to be preserved across pages in different modules.
I structured it as one solution with different Web Projects and one class library project with common functionalities.
1) is this the right approach to do this? Or which one would be better?
2) each time I add a new web project to the solution, a new web.config gets created. What do I do and where do I put them?
VS 2010 + framework 4.0 + TFS
Regarding TFS and source control, I have a single Team project, the solution and web projects are inside it.
I'm trying to rewrite my urls, which kinda work now.
The problem is that in my page i'm using a timer to refresh the data every couple of seconds.But in Mozilla firebug I can see that the url keeps changing: it's getting bigger after each timer update, like this:
etc etc, until it returns a 404 not found.
What can I do to prevent this?
Alsalamo 3alaykom ,
as we know that if you use Intelligencia.UrlRewriter.RewriterHttpModule or IIS URL Rewriting , we will face problems with arabic urls
http://localhost:1234/Pages/???? ?????? ?????? ??????????
and the Rule is :
<rewrite url="~/Pages/(.+)" to="~/ShowPages.aspx?Page=$1" />
you will recive the QueryString["Page"] Like this
Ãâ¢Ã¢â¬Â ÃËÃÂ§ÃËÃÂ¦ÃËÃÂ¨ ÃËÃÂ§Ãâ¢Ã¢â¬Å¾ÃËÃÂ¹Ãâ¢Ã¢â¬Â¦Ãâ¢Ã
Â ÃËÃÂ¯ Ãâ¢Ã¢â¬Å¾Ãâ¢Ã¢â¬Å¾ÃËÃÂ´ÃËÃÂ¤Ãâ¢Ãâ Ãâ¢Ã¢â¬Â ÃËÃÂ§Ãâ¢Ã¢â¬Å¾ÃËÃÂ£Ãâ¢ÃâÃËÃÂ§ÃËÃÂ¯Ãâ¢Ã
so it's a big problem , and there is a solution that is :
remove the Rule of that rewriting ,,
<rewrite url="~/Pages/(.+)" to="~/ShowPages.aspx?Page=$1" />
then open your Global.asax file and Application_BeginRequest method exactly
use the following code to handle you request
void Application_BeginRequest(object sender, EventArgs e)
String txt= Regex.Split(HttpContext.Current.Request.Url.ToString(), @"/");
String page = txt[txt.Length-1];
This article explains how you can use Active Directory Federation Services (AD FS) 2.0 to claims-enable Windows Communication Foundation (WCF) services and browser-based applications. The focus is on the token issuance functionality in AD FS 2.0. You'll find out how to use AD FS 2.0 as an identity provider; set up an AD FS 2.0 security token service (STS) to interact with WCF; federate AD FS 2.0 with your custom STS or another AD FS 2.0; enable Web single sign-on and federation with WS-Federation and SAML 2.0 protocols; and externalize authentication logic through Visual Studio. You'll come away appreciating how AD FS 2.0 and Windows Identity Foundation make programming identity solutions in Windows less of a chore.
MSDN Magazine November 2009
The challenge in SharePoint development has always been the balance between creating and deploying solutions that you can trust not to damage or impair a SharePoint farm. A new feature in SharePoint 2010, called Sandboxed Solutions, enables farm administrators to feel comfortable that the SharePoint farm is safe, gives site collection administrators the authority to manage applications in their site collection, and provides developers with the flexibility to create solutions they know will be deployed in a safe and rapid manner.
We introduce you to the EDI functionality within BizTalk Server 2006 R2, illustrating schema creation, document mapping, EDI delivery and transmission, and exception handling.
MSDN Magazine August 2008
One-time passwords offer solutions to dictionary attacks, phishing, interception, and lots of other security breaches. Here's how it all works.
MSDN Magazine May 2008
OBA solution patterns help architects and developers build Office Business Applications (OBAs). This article introduces the seven core OBA solution patterns and applies one to a real-world problem.
MSDN Magazine March 2008
WSS 3.0 introduces a new deployment mechanism that lets you move your development efforts into a staging or production environment.
MSDN Magazine August 2007
State management in Web applications is a contentious issue. Should you store user data per session or should you persist it across sessions? You can easily store information temporarily while someone navigates your site by using session state.
MSDN Magazine April 2006
I love the part of my job that lets me write code and develop software. In addition to those responsibilities, however, I manage a development organization that's working on a number of large strategic projects.
Larry W. Jordan Jr.
MSDN Magazine March 2005
Timers often play an important role in both client applications and server-based components (including Windows services). Writing effective timer-driven managed code requires a clear understanding of program flow and the subtleties of the .NET threading model. The .NET Framework Class Library provides three different timer classes: System.Windows.Forms.Timer, System.Timers.Timer, and System.Threading.Timer. Each of these classes has been designed and optimized for use in different situations. This article examines the three timer classes and helps you gain an understanding of how and when each class should be used.
MSDN Magazine February 2004
You could execute a function call that is not allowed in the sandbox (for example call a static method on SPSecurity) and catch the exception. A better approach is to test the friendly name of you app domain:
AppDomain.CurrentDomain.FriendlyName returns "Sandboxed Code Execution Partially Trusted Asp.net AppDomain"
Because you can never be sure that this string changes in the future, a safer approach will be:
See http://www.sharepointoverflow.com/questions/2051/how-to-check-if-code-is-running-as-sandboxed-solution for a discussion on this topic.