.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Deploying on a Web Farm

Posted By:      Posted Date: October 04, 2010    Points: 0   Category :ASP.Net

I use session variables - and unfortunately my website is deployed on GoDaddy's shared server environment.  Hopefully we will be successful and be able to get their dedicated server services soon.

As you can imagine, sometimes the server farm moves my hosting from one server to another and *poof* - all the session variables evaporate, and down she goes with a crash!

Is there a way to handle this?  Will switching to sql to store session variable values work (what is the term for that)?

View Complete Post

More Related Resource Links

Deploying a custom theme as a farm solution

Hello,   I am a beginner to Visual Studio 2010 + Sharepoint 2010 - I have created a custom theme and would like to deploy it to my dev Sharepoint farm as a solution.  I've added the "Sharepoint mapped folder.." (..TEMPLATE\GLOBAL\Lists\themes) and added my thmx to that folder in the project.  When the solution is deployed to my dev farm the custom theme gets added to the 14 hive \TEMPLATE\GLOBAL\Lists\themes folder but when a new site is created the theme is not available from Site Settings->Site Theme or in the Theme Gallery.  What am I missing here?

Deploying a .thmx theme as a farm solution


Hello everybody,

I am another beginner to Visual Studio 2010 + SP 2010 and I have created:

1.     A custom theme (.thmx file)

2.     A feature to deploy it to my SharePoint farm as a solution, and this is how the FeatureActivated method look like:

        public override void FeatureActivated(SPFeatureReceiverProperties properties)

            SPWeb currentWeb = (SPWeb)properties.Feature.Parent;

            currentWeb.AllowUnsafeUpdates = true;

            currentWeb.SiteLogoUrl = "**url to logo1**";


            foreach (ThmxTheme theme2 in ThmxTheme.GetManagedThemes(currentWeb.Site))

BDC/BCS Model doesn't show up when deploying custom bcs solution to farm



I've created a custom BCS solution in VS2010, for SP2010, it's based on a .net assembly and in dev/test it all works fine.

Unfortaunetly, when I package it for production, although it deploys successfully - or so everything says - if I look in Central Admin for the BDC model, it's not there!

Has anybody else come across the same issue?

Please let me know what other information you might need.

Kind regards,


Custom Timer Job deploying at Farm level



I am trying to develop a timer job that is deployed at Farm Level. can anyone point me to an example of how to deploy it?

(I am looking for code in FeatureActivated and deactivated event)



deploying to msdeploy does not support a proxy server


I am trying to deploy through webmatrix but my system Proxy server configuration is not being used. I assume that webmatrix would detect the proxy server settings and use that for the msdeploy calls under the hood. Can anyone confirm this is a know issue? 

Windows Azure: Developing and Deploying Cloud Apps in Visual Studio 2010


You'll find direct support for building Windows Azure applications in Visual Studio 2010 and Visual Web Developer 2010 Express. We'll walk you through using Visual Studio 2010 for the entirety of the Windows Azure application development lifecycle.

Jim Nakashima

MSDN Magazine April 2010

Cloud Patterns: Designing and Deploying Services for Windows Azure


To better understand how SOA patterns can be applied to Windows Azure deployments, we walk you through a scenario in which a bank moves its services to the cloud.

Thomas Erl, Arman Kurtagic, Herbjörn Wilhelmsen

MSDN Magazine January 2010

SharePoint's Sandbox: Developing, Deploying and Monitoring Sandboxed Solutions in SharePoint 2010


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.

Paul Stubbs

MSDN Magazine November 2009

Code Name Longhorn: A First Look at Writing and Deploying Apps in the Next Generation of Windows


The next version of the Microsoft Windows operating system, code-named "Longhorn," marks a significant change not only in terms of how the operating system works, but also in the way in which applications are built. The Longhorn version of Windows includes a new storage system, natural search technology, and an increased emphasis on security and trustworthy computing. Here the author provides an overview of Longhorn, focusing on the build-once, deploy n-times application model. In addition, he discusses the new language, code-named "XAML," that's used to create UI elements, then presents some working samples.

Dino Esposito

MSDN Magazine January 2004

The ASP Column: Deploying an ASP.NET App Using Visual Studio .NET


When Visual Studio® . NET was released back in February 2002, it included a number of new features that made it easier to create Web applications. The Microsoft® . NET Framework includes classes for intercepting and processing HTTP requests, and Visual Studio .

George Shepherd

MSDN Magazine November 2002

ASP.NET Security: An Introductory Guide to Building and Deploying More Secure Sites with ASP.NET and


Forms authentication is one of the most compelling and useful new features of ASP.NET. It enables developers to declaratively specify which files on their site can be accessed and by whom, and allows identification of a login page. When an unauthenticated user attempts to retrieve a page protected by forms authentication, ASP.NET automatically redirects them to the login page and asks them to identify themselves. Included here is an overview of forms authentication and what you need to know to put it to work. Also included is hard-to-find information on the security of cookie authentication and on combining forms authentication with role-based URL authorizations.

Jeff Prosise

MSDN Magazine May 2002

ASP.NET Security: An Introductory Guide to Building and Deploying More Secure Sites with ASP.NET and


ASP.NET and Microsoft Internet Information Services (IIS) work together to make building secure Web sites a breeze. But to do it right, you have to know how the two interrelate and what options they provide for securing access to a Web site's resources. This article, the first in a two-part series, explains the ABCs of Web security as seen through the eyes of ASP.NET and includes a hands-on tutorial demonstrating Windows authentication and ACL authorizations. A range of security measures and authentication methods are discussed, including basic authentication, digest authentication, and role-based security.

Jeff Prosise

MSDN Magazine April 2002

.NET Framework: Building, Packaging, Deploying, and Administering Applications and Types-Part 2


Part 1 of this series discussed how types built for the common language runtime can be shared among applications in the Microsoft .NET Framework regardless of the .NET languages used to build them. This second part continues with building assemblies by first covering security, sharing assemblies, versioning, localization, and side-by-side execution. Because in .NET two DLLs with the same name can be loaded as long as another attribute-which can include the localization language-differs, versioning is much easier than it used to be, so DLL Hell may become a thing of the past.

Jeffrey Richter

MSDN Magazine March 2001

.NET Framework: Building, Packaging, Deploying, and Administering Applications and Types


Types that are built for the Common Language Runtime can be shared among applications in the Microsoft .NET Framework no matter which of the .NET languages they were built in, an obvious benefit to developers. This article describes the building, packaging, and deploying of applications and types for the .NET Framework, including the role and significance of assemblies, private and otherwise. The way metadata and assemblies help to solve some historical problems like versioning conflicts and DLL Hell, and how they improve system stability are also discussed.

Jeffrey Richter

MSDN Magazine February 2001

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend