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


Top 5 Contributors of the Month
Imran Ghani
Post New Web Links

Third part plug-in deployment in web application?

Posted By:      Posted Date: September 15, 2010    Points: 0   Category :ASP.Net
 
I developed a Java Applet for asp.net c# web application, my question is : How should I deploy this Java Applet in my  msi file , I hope that one expert can give me detailed steps for how to put the java applet into msi file?Thanks.


View Complete Post


More Related Resource Links

Application Architecture: An N-Tier Approach - Part 1

  
Introduction

Free Trial: SQL Backup Pro
Sponsored by Red Gate
Exceptional DBAs make the most of their office hours. That's why they love Red Gate SQL Backup Pro. Its faster, smaller, secure SQL Server backups mean more time spare to accomplish more tasks and professional training. Make time to be an Exceptional DBA. Download it now! »


Free Trial: SQL Toolbelt
Sponsored by Red Gate
The SQL Toolbelt is a set of twelve powerful and intuitive tools that will help you burn through SQL Server chores with astonishing speed and accuracy. Download it now! »


Download: SQL Backup Evaluation Center
Sponsored by Red Gate
Download the T-SQL scripts in the SQL Backup Evaluation Center to compare Red Gate SQL Backup Pro's compressed backups with the size of backups created using native SQL Server. Download it now! »



MARKETPLACE
Autodesk Inventor®
Go Beyond 3D To Digital Prototyping With Autodesk Inventor. Learn How.
Autodesk.com/Beyond-3d
Virtualization Solutions
Optimize, Simplify, & Save Today. Learn About Microsoft Solutions.
www.microsoft.com
Microsoft SQL Server® 2008 - Free Trial
Download the Free 180-day Trial of SQL Server® 2008 Enterprise Edition!
www.Microsoft.com/SQLServer
Hot Careers in Internet Marketing
Get prepared for your new career with online degrees from Full Sail University!
www.FullSail.edu
Microsoft Te

SharePoint Application and Site Pages - Part 1 of 2

  
In this first part of the two part series, Steven covers the differences between Site and Application pages in SharePoint 2007, why each may be used in various circumstances, and prepares for the construction of a menu located application page. After a brief introduction he examines the concept of Site Pages and Application Pages separately in detail with supported screenshots.

SharePoint Application and Site Pages - Part 2 of 2

  
As the second article in a two part series, Steven examines the attributes and details of a SharePoint 2007 application page, including the construction and feature deployment of the same page based project. Since this is a WSS level objective, as opposed to MOSS, you will not need MOSS to work with the code included in this project. Windows Server 2003, WSS, and Visual Studio 2005 are all that is needed, with no additional add-ons. He provides a detailed analysis of each step involved in the creation and deployment of the project.

Cutting Edge: AJAX application architecture, Part 2

  

The second of this two-part series delves into the script services programming model, which is useful if you're looking for a full paradigm shift in building AJAX applications.

Dino Esposito

MSDN Magazine October 2007


Cutting Edge: AJAX Application Architecture, Part 1

  

In the first of a two-part column, Dino explains AJAX from an architectural standpoint to help developers, architects, designers, and administrators better understand the issues that affect their sites.

Dino Esposito

MSDN Magazine September 2007


Data Points: The Enterprise Library Data Access Application Block, Part 3

  

E nterprise applications can have a wide variety of data update requirements. Sometimes you need to save multiple rows of changes at once within a single transaction. Other times, the user must be allowed to enter multiple rows of data, send them to the database in a batch; and if a row or two fails, only the rows that succeeded should be committed and remain committed.

John Papa

MSDN Magazine October 2005


Data Points: The Enterprise Library Data Access Application Block, Part 2

  

Last month I explored the foundation of the Enterprise Library Data Access Application Block (DAAB) including how it all fits into an architecture (see Data Points: The Enterprise Library Data Access Application Block, Part 1).

John Papa

MSDN Magazine August 2005


Data Points: The Enterprise Library Data Access Application Block, Part 1

  

A solid data access later (DAL) can benefit an application by hiding redundant tasks, helping handle exceptions more gracefully, helping clean up resources more efficiently, and providing a layer of abstraction from the database.

John Papa

MSDN Magazine July 2005


Web Security: Part 2: Introducing the Web Application Manager, Client Authentication Options, and Pr

  

This article, the second of two parts, continues coverage of Web security for Windows. It introduces the Web Application Manager in IIS that allows Web processes to be isolated, decreasing the security risk associated with running in a logon session. The article then picks up where Part One left off-it discusses authentication methods such as basic authentication, digest authentication, integrated Windows authentication, and anonymous logons, and the benefits and drawbacks of each.

Keith Brown

MSDN Magazine July 2000


Web Part Versioning and Deployment (properties only)

  

Suppose I have a 3<sup>rd</sup> party Web Part (source code provided, with Web Part deployed as a Feature) that’s installed and used in several Sites within a Site Collection.  I want to make changes not to the source code (which would require updating the assembly and deploying the changes as an updated Feature/Solution Package), but to property values of the Web Part that exist.  Say the WP exists on 10 pages, and I want to change the WP’s Title property from “Amazing Vendor Web Part” to “My New Title”.

 

First, would this be considered an “out-of-band” patch?  Not that it matters terribly how to label this…

 

Second, would the ideal approach be to simply add code within a Feature Receiver in that Web Parts VS project (the Feat

Web Part Namespace & Deployment Question

  

Hi,

I have a web part deployment and development question. Probably newbie questions..

For web parts which will only be used in certain web applications, I can definitely see creating custom CAS policies etc.. and deploying the dll only to the Bin of the Web Application, but what is the best practice for deploying a Farm wide web part that everyone will use?

I assume it goes in the GAC, and additionally, are there any best practices as far as the namespaces for web parts when they are going into the GAC?

For example, if I go into the Assembly folder and look at all the assemblies in the GAC, is it "okay" to have various globally deployed web part assemblies in there? Like, "MyCustomWebPart" sitting in there with the other sharepoint assemblies? Seems messy to me, but if these are "one-off" web parts that won't have a bunch of classes within a single namespace, it seems like what needs to be done.


Hopefully that was clear enough!


Problem with precompiling web application for deployment

  
Hi,I'm developing a web application consisting of several DLLs. I have no problem whatsoever compiling en building the application from within Visual Studio 2008 itself. But when I try to precompile the application (for deployment) from the VS command prompt, I get compilation errors.One of the errors is: "Could not load file or assembly 'wsCore' or one of its dependecies. The system cannot find the file specified".How can it be that VS2008 is perfectly capable of compiling the application from within the IDE and that same application can't be compiled from the command prompt?What am I missing here?

Import Error: Could not process the file Documents/Application Deployment.mht as a Single File Web P

  
Hi there everyone, Version: Windows Sharepoint Services 3.0 with Cumulative Update June 29, 2010 applied. I am having issues importing an exported site into a different domain. I've overcome most of the issues and actually got most of the site to import, however, the import process get's stuck on import a Single File Web Page document from a document library. I believe the original cause of this error is http://support.microsoft.com/kb/980079 The issue I face now is, I already have a large number of .mht files in my document library which I do need to import into the test environment (or that I might need to restore in a DR scenario). Does anyone have any information on either: forcing the import commmand to "on error resume next" (ie. not stop processing when it encounters an error) fixing the already corrupt .mht files in the database easily The error text from the import command is: Error: Could not process the file Documents/Application Deployment.mht as a Single File Web Page document. at Microsoft.SharePoint.Library.SPRequest.CreateOrUpdateFileAndItem(String bstrUrl, String bstrWebRelativeUrl, Guid& docId, Object varDoc, Int32 docLength, Int32 exists, String bstrCreatedBy, String bstrModifiedBy, Int32 iCreatedByID, Int32 iModifiedByID, Int32 iVersion, Object varTimeCreated, Object varTimeLastModified, Object varProperties, String checkInComment, Int3

Reg deployment of console application to customer

  
Hi, First I have written code in class library file so that Title field should not allow duplicate values as follows using Microsoft.SharePoint;     public class UniqueIdEventHandler:SPItemEventReceiver     {         const string TITLE_QUERY = @"<Query><Where><Eq><FieldRef Name=""Title"" /><Value Type=""Text"">{0}</Value></Eq></Where></Query>";           public override void ItemAdding(SPItemEventProperties properties)         {             if (properties.AfterProperties["Title"] != null)             {                 //get the title of the new item                 string currentTitle = properties.AfterProperties["Title"].ToString();                 //get the web site object                 using (SPWeb

Reg deployment of console application to customer

  
Hi, First I have written code in class library file so that Title field should not allow duplicate values as follows using Microsoft.SharePoint;     public class UniqueIdEventHandler:SPItemEventReceiver     {         const string TITLE_QUERY = @"<Query><Where><Eq><FieldRef Name=""Title"" /><Value Type=""Text"">{0}</Value></Eq></Where></Query>";           public override void ItemAdding(SPItemEventProperties properties)         {             if (properties.AfterProperties["Title"] != null)             {                 //get the title of the new item                 string currentTitle = properties.AfterProperties["Title"].ToString();                 //get the web site object                 using (SPWeb
Categories: 
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