How to retrieve People Picker AD id and Display name to store in the SQlL Server Databases
Tuesday, August 7, 2012
Wednesday, July 18, 2012
Friday, June 29, 2012
Friday, May 25, 2012
Sharepoint 2007 Timer Job Development and Deployment Steps
Sharepoint 2007 Timer JobCreate Timer job solution File.1.Create C# project Library2.Create Timer.CS, TimerInstaller.CS, Feature.xml, manifest.xml files 3.Copy existing code and past it in the proper files 4.Set strong name 5.Build DLL 6.Copy DLL id in the feature file 7.Build WSP and following deploying procedures. Deployment Timer Jobs:1. C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES 1.1 Create a folder " KarNet.TimerJob " 1.2 Copy the files "Feature.xml" & "Manifest.xml"2. Run the install.bat file to deploy the Solution file. 2.2 before that edit the file to point to correct SharePoint site, by changing the "TargetUrl". 2.3 stsadm -o installfeature -name KarNet.TimerJob -force 3. Copy the KarNet.TimerJob.DLL to GAC. 4. Activate the Site Collection feature to enable the custom Timer 5. Restart the Timer Service in services. 6. Create a Folder in C:\ as "KarNetLog" 7. Share the folder and allow "everyone" full access. Activate Feature manuallyC:\Program Files\Common Files\Microsoft Shared\web serverextensions\12\BIN>stsa dm -o deactivatefeature -name KarNet.TimerJob -url "http://KarNet-46b4a490b" C:\Program Files\Common Files\Microsoft Shared\web serverextensions\12\BIN>stsa dm -o uninstallfeature -name "KarNet.TimerJob" C:\Program Files\Common Files\Microsoft Shared\web serverextensions\12\BIN>stsa dm -o installfeature -name KarNet.TimerJob -force C:\Program Files\Common Files\Microsoft Shared\web serverextensions\12\BIN>stsa dm -o activatefeature -name "KarNet.TimerJob" -url "http://KarNet-46b4a490b " Timer .csTimerInstaller.csFeature.xmlmanifest.xml |
ASP.Net Server side POP UP message box displayed
The below code is working in the server side of the ASP.Net
code, You have to modify only the panel name based on you form
System.Web.UI.ScriptManager.RegisterClientScriptBlock(panel1, Page.GetType(), "strscript", "alert('Record Successfully Updated.')", true);
System.Web.UI.ScriptManager.RegisterClientScriptBlock(panel1, Page.GetType(), "strscript", "alert('Record Successfully Updated.')", true);
Saturday, March 31, 2012
Error: InfoPath cannot load the view... unsupported HTML such as framesThe following HTML tag is not supported:'comment'
It may have a corrupted form.
Infopath forms (in 2007 anyway) are actually just Microsoft CAB files. Youcan rename a form from .xsn to .cab and then open it using any aplicationthat understands cab files.
There are a number of files in each CAB file, but the ones you areinterested in are probably the *.XSL (there is one for each InfoPath "View"plus some extras) and the manifest.xsf file which is like the "table ofcontents".WARNING!!! DANGER WILL ROBINSON!!! etc etcThis isn't for the faint-of-heart, but you did say you were desperate...
You may have to run through a combination of:
1. Renaming the .XSN to .CAB
2. Expanding the .CAB file
3. Hacking either the individual xsl views and/or the manifest.xsf to removethe offending view(s)
4. Repacking the CAB file
5. Renaming back to .XSN
6. Open in Infopath, hope error is gone
This has only happened to me once - I ended up having to delete theoffending view and recreate it. To find out which view was broken, I had todelete each view, reopen, repeat until I found out which of the views wasbroken. Worked for me (we had about 30 very complex views) and saved a wholelot of time.
Repacking the extracted files of infopath back to .xsn
Right-click on the manifest.xsf, select Design, save as xsn.
Infopath forms (in 2007 anyway) are actually just Microsoft CAB files. Youcan rename a form from .xsn to .cab and then open it using any aplicationthat understands cab files.
There are a number of files in each CAB file, but the ones you areinterested in are probably the *.XSL (there is one for each InfoPath "View"plus some extras) and the manifest.xsf file which is like the "table ofcontents".WARNING!!! DANGER WILL ROBINSON!!! etc etcThis isn't for the faint-of-heart, but you did say you were desperate...
You may have to run through a combination of:
1. Renaming the .XSN to .CAB
2. Expanding the .CAB file
3. Hacking either the individual xsl views and/or the manifest.xsf to removethe offending view(s)
4. Repacking the CAB file
5. Renaming back to .XSN
6. Open in Infopath, hope error is gone
This has only happened to me once - I ended up having to delete theoffending view and recreate it. To find out which view was broken, I had todelete each view, reopen, repeat until I found out which of the views wasbroken. Worked for me (we had about 30 very complex views) and saved a wholelot of time.
Repacking the extracted files of infopath back to .xsn
Right-click on the manifest.xsf, select Design, save as xsn.
Subscribe to:
Posts (Atom)