When stand-alone WSS is installed on a machine which doesn’t have SQL 2005 standard edition or higher installed, the setup installs a special embedded edition of SQL Server with an instance name Microsoft##SSEE. By default settings, this SQL server is not exposed to the outside world and you will not be able to connect to it from management studio. But there might be situations which require connecting to this embedded SQL server. Following steps explains this process.
Open SQL Configuration Manager from Programs -> Microsoft SQL Server 2005 -> Configuration Tools.
Expand the SQL Server 2005 Network Configuration node.
Right, click on Protocols for the Microsoft##SSEE instance and select properties.
From the properties window that shows up select HideInstance property and changes its value to No.
Click OK to close the properties window.
Restart the embedded Microsoft##SSEE SQL server instance using the Surface Area Configuration Tool.
Now you will be able to connect to the WSS embedded Microsoft##SSEE SQL server instance from SQL server management studio using windows authentication.
https://www.iotap.com/wp-content/uploads/2019/02/iotap_logo_transparent-2.png00kjawalehttps://www.iotap.com/wp-content/uploads/2019/02/iotap_logo_transparent-2.pngkjawale2008-11-11 13:04:292019-10-14 12:02:47Cannot Connect to Windows SharePoint Services (WSS) Internal Database Microsoft##SSEE
Visual Studio 2008 extensions for Sharepoint greatly ease the process of developing custom Sharepoint solutions. The extension provides a set of visual studio templates for rapid creation of Sharepoint Web Parts, Content Types, and Modules etc. You can download the extensions from this Microsoft link.
Using this extension creating and deploying a webpart is just a breeze and everything works to perfection for the first web part we create. But troubles arise when we start deploying subsequent web parts. During deployment of subsequent webparts Visual Studio 2008 comes up with the following error message.
“The feature name WebPart1 already exists in SharePoint. You need to rename the feature before solution deployment can succeed.”
This error happens even if you are given a different name for your web part file and web part class file. This is because behind the scenes Visual Studio stores the solution name as Webpart1 even if you have given a different name to your webpart. To overcome this VS 2008 behavior, the following changes have to be made to the webpart feature files.
Change the name of webpart folder, webpart xml and webpart files from Webpart1 to the name of your web part for e.g. WP1. So in effect, the folder WebPart1 will become WP1, the file WebPart1.webpart will become WP1.webpart and the file WebPart1.xml will become WP1.xml.
Select the Show All Files option from VS 2008 Solution Explorer toolbar.
Three additional folders namely bin, obj, pkg will be displayed in grayed out style.
Expand the pkg folder. Pkg folder will have a subfolder named Webpart1 and two XML files manifest.xml and solution.xml.
Rename Webpart1 folder name to your webpart for e.g. WP1
Edit solution.xml and change the name of feature from Webpart1 to your webpart name
This will hide the whole Welcome Panel when the page is displayed in the web browser. Do not remove the welcome.ascx control from the Controltemplate folder.
The welcome menu is part of the link itself. It’s a whole functionality which is contained in welcome.ascx. So if you remove that, you will lose the menu too.
Step 2:
Create the ASPX for an admin user called adminlogin.aspx
The “Sign In” link available in the top-right corner of the Sharepoint site except the admin page.
https://www.iotap.com/wp-content/uploads/2019/02/iotap_logo_transparent-2.png00kjawalehttps://www.iotap.com/wp-content/uploads/2019/02/iotap_logo_transparent-2.pngkjawale2008-10-15 13:09:262019-10-14 12:03:47Hide Sign-In Link on the SPSites Except Admin Page
Visual Studio 2008 extensions for Sharepoint greatly ease the process of developing custom Sharepoint solutions. The extension provides a set of visual studio templates for rapid creation of Sharepoint Web Parts, Content Types, Modules etc. You can download the extensions from this Microsoft link.
This blog entry details the steps involved in debugging a web part created using visual studio 2008 web part template. The steps listed are for the scenario where Sharepoint and visual studio exists on the same machine.
Steps
1. Develop the Sharepoint web part using VS 2008 web part project template. 2. Deploy the web part. With VS 2008 you don’t have worry about manifest and WSP files. Just right-click on the project name in solution explorer and select Deploy. 3. Add the web part to a Sharepoint page. 4. Set up breakpoints in your web part code. This similar to setting up breakpoints in any .Net code. 5. Attach debugger to ASP.Net worker process (w3wp.exe)
a. From the VS 2008 Debug menu select Attach to Process option b. From the list of running processes that show up select w3wp.exe and click Attach button.
c. If a recent iisreset was performed on your machine, you must navigate to the Sharepoint site to create a new instance of w3wp process. d. Sometimes you may also find multiple w3wp process showing up in the Attach Processes list. In such situations you can follow any of the below methods
i. Attach debugger to all w3wp.exe processes. This will ensure that you attach to the process that is running your web part. ii. You can kill all the w3wp.exe processes by using iisreset /noforce from the command line and navigating to the Sharepoint site to create a new w3wp instance.
6. Navigate to the Sharepoint page which contains the web part you want to debug. 7. As the page starts rendering, control will be transferred to the visuals studio code editor with the execution stopping at first break point. 8. You can continue debugging as with any .Net code.
https://www.iotap.com/wp-content/uploads/2019/02/iotap_logo_transparent-2.png00kjawalehttps://www.iotap.com/wp-content/uploads/2019/02/iotap_logo_transparent-2.pngkjawale2008-10-14 13:11:132019-10-14 12:04:00Debugging SharePoint Webpart from VS 2008
• Accelerators are contextual services which quickly access a service from any webpage. • Users often copy and paste from one webpage to another, but Internet Explorer 8 accelerators make this easier. • Accelerators enable users to find information without leaving the current webpage.
Accelerator Categories
With Accelerators, you can do tons of great things…
• Blog
Share your life online with Blogger.
• Define
Get definitions.
• Map
View maps and directions.
• Send
Send with Gmail.
• Translate
Select content in other languages.
This is a simple sample that shows a map accelerator that you can host on a website
Host the install button: Add this code example to the website on which you want to advertise the accelerator.
• AddService
To install XML-based Accelerators
• IsServiceInstalled
To verify whether the user currently has the Accelerator installed.
Create the accelerator XML file: Copy the sample code below to a text editor and save it as “GetMap.xml”. This code below describes the functionality of the accelerator.
os:homepageUrl Required. The os:homepageUrl element defines the main URL of the Accelerator—where the user can access the service through browsing. All URLs declared in the OpenService Accelerator file must use the same domain as that of the os:homepageUrl.os:display
os:name Required. The os:name of the Accelerator that is displayed to the user on the context menu. Accelerator names should lead with a verb followed by the service provider.
os:icon Optional. The os:icon element provides a URL to a 16 x 16 pixel icon for this Accelerator. The domain name used must match the os:homepageUrl.
os:description Optional. The os:description element provides a longer description for the Accelerator that is displayed in the Manage Add-ons dialog box.
os:activity Required. The os:activity element contains all of the functionality of an Accelerator.os:activityAction – interaction with the accelerator.We have document,selection,link. Default Selection.
os:preview Optional. The os:preview element defines the content of the HTML window displayed when the user hovers over the Accelerator. It shares the same attributes and child elements as the os:execute element.
os:execute Required. The os:execute element specifies the main action triggered when the user invokes the Accelerator. Like os:preview, it can contain replacement variables in the action attribute or as separate os:parameter elements.
os:parameter Optional. The os:parameter element provides an alternative way to express the values to use. The required name and value attributes define string inputs that are specific to the service and typically refer to Accelerator variables. See the Variables section for a list.
Test the accelerator:
• Install the accelerator by clicking Install on your website. This launches the installation dialog box. • Select the Make this my default provider check box. This sets the accelerator to appear in the top listing. • Go to a site that contains a street address. • Select the address and click the button that appears next to the mouse cursor. (Alternatively, you can right-click to get the context menu.) • Hover over the Map with MyGoogleMap accelerator. This displays the preview of the map accelerator. • Click the Map with MyGoogleMap accelerator. This navigates to the map website in a new tab.
https://www.iotap.com/wp-content/uploads/2019/02/iotap_logo_transparent-2.png00kjawalehttps://www.iotap.com/wp-content/uploads/2019/02/iotap_logo_transparent-2.pngkjawale2008-10-07 13:16:352019-10-14 12:04:15How We Can Create Accelerator in Internet Explorer 8 Beta
Web Slices is a new feature enabling websites to connect to their users by subscribing to content directly within a webpage. Web Slices behave just like feeds where clients can subscribe to get updates and notify users of changes.
A Web Slice is a section of a webpage that is treated like a subscribable item, just like a feed. To enable a Web Slice on your website, annotate your webpage with class names for the title, description, and other subscribable properties.
• Navigating to a Different Web Page <div class=”hslice” id=”3″> <h2 class=”entry-title”>Search</h2> <a rel=”bookmark” href=”http://www.Google.com” style=”display:none;” ></a> </div>
• Enable or disable the Webslice for all sites – Tools->Internet Options – Under the Content tab – Click Settings of Feed – Select or deselect the “Turn on in Page Webslice discovery”
• Turn on or off Webslice discovery for a specified websites <meta name=”slice” scheme=”IE” content=”on”/>
or
<meta name=”slice” scheme=”IE” content=”off”/>
• webslice icons with various sizes
• We can control the Webslice duration using endtime property : Expiration time for a Web Slice. The inner text will be disabled after expiration.
The hslice element contains all of the required and optional properties of a Web Slice.
• entry-title
Title of the webslice.
• entry-content
Content of the Webslice
https://www.iotap.com/wp-content/uploads/2019/02/iotap_logo_transparent-2.png00kjawalehttps://www.iotap.com/wp-content/uploads/2019/02/iotap_logo_transparent-2.pngkjawale2008-10-07 13:14:352019-10-14 12:04:35How We Can Create WebSlices in Internet Explorer 8 Beta
All OpenSearch Description files must include the search provider name and search URL. Without these elements, Internet Explorer 8 cannot install your search provider. All search URLs must contain “q={searchTerms}” somewhere in the query string. When Internet Explorer 8 navigates to this provider to get search results, “{searchTerms}” is replaced by the query string that the user typed into the Instant Search box. you should include an icon within the OpenSearch Description file.
https://www.iotap.com/wp-content/uploads/2019/02/iotap_logo_transparent-2.png00kjawalehttps://www.iotap.com/wp-content/uploads/2019/02/iotap_logo_transparent-2.pngkjawale2008-10-07 13:12:502019-10-14 12:04:49How We Can Create Search Provider in Internet Explorer 8 Beta
Did you get the following message will be a turn-on when loading public Sharepoint sites,
The Web site wants to run the following add-on: ‘Name ActiveX Control’ from ‘Microsoft Corporation’. If you trust the Web site and the add-on and want to allow it to run, click here…
To fix this problem, just create a js file and paste the following codes to that file,
function ProcessDefaultOnLoad(onLoadFunctionNames) { ProcessPNGImages(); UpdateAccessibilityUI(); for (var i=0; i < onLoadFunctionNames.length; i++) { var expr=”if(typeof(“+onLoadFunctionNames[i]+”)==’function’){“+onLoadFunctionNames[i]+”();}”; eval(expr); } if (typeof(_spUseDefaultFocus)!=”undefined”) DefaultFocus(); }
And then upload the javascript file to SharePoint site. After the above process, then refer the javascript file link to SharePoint master page. Now you didn’t get any ActiveX Control problem. For more information Email us.
https://www.iotap.com/wp-content/uploads/2019/02/iotap_logo_transparent-2.png00kjawalehttps://www.iotap.com/wp-content/uploads/2019/02/iotap_logo_transparent-2.pngkjawale2008-10-03 13:20:182019-10-14 12:05:42Solving ActiveX Problem in SharePoint
The SharePoint takes the Default zone link in Alternate Access Mappings for all links when creating alerts. To overcome this issue, add the required URL in default zone textbox in Alternate Access mappings and change the URL already in Default zone to different zone.
If you are applying custom Master page using the custom feature, you may get the following error when viewing or creating a new site,
Cannot convert type ‘Microsoft.SharePoint.WebControls.ScriptLink’ to ‘System.Web.UI.IAttributeAccessor’
This is because; you are exporting the master page using SharePoint Designer. The master page adds the additional codes; you will be seeing that by open via notepad.