If you want to develop cross platform mobile applications then you must have heard of Xamarin platform. Good news is Microsoft has now integrated its product suite as its offering inside Visual Studio.
You can install Xamarin from Visual Studio setup, if in case you are getting the following error – no need to worry as there is a manual way to get it installed.
Please download and install following packages (in same order) in the steps listed below to overcome the error shown above:
- JDK 1.7: http://download.xamarin.com/Installer/MonoForAndroid/jdk-7u71-windows-i586.exe
- Android SDK: http://dl.google.com/android/installer_r24.0.2-windows.exe
- GTK#: http://download.xamarin.com/GTKforWindows/Windows/gtk-sharp-2.12.26.msi
- Xamarin Studio: http://download.xamarin.com/studio/Windows/XamarinStudio-188.8.131.52-0.msi
- Xamarin for Windows (includes Xamarin.iOS for Visual Studio and Xamarin.Android): http://download.xamarin.com/XamarinforVisualStudio/Windows/Xamarin.VisualStudio_3.9.547.msi
Once above packages are installed, you are good to start your cross platform mobile development on windows platform. Your visual studio will show the products are installed as shown below:
Next step is to connect your Visual Studio with Mac, for that you need to ensure following on your Mac machine:
- A Mac running OS X Yosemite (10.10) or higher
- Xamarin Studio 5.10 or higher (Note: This should be on the same distribution channel as Xamarin for Visual Studio)
- Xamarin.iOS SDK.
- Apple’s Xcode(7+) IDE and iOS SDK (latest version).
- Create and configure Apple account
- Create and configure Xamarin account for Xamarin Studio
Once you have downloaded and installed the above packages on Mac, you are good to start your mobile development from Visual Studio which is connected with Mac.
Open Visual Studio, and go to tool where you will find an option for Xamarin – once you have connected your Visual Studio with Mac it will show you this screen with the name of Mac connected for your development.
If your dev machine is connected with Mac, you can start developing applications – create a new project in Visual Studio of type iOS and then select single view App and your Visual Studio will show you screen like the one below:
If all of the above steps are done successfully then happy .NET coding for cross platform mobile development 🙂 more posts to come….
As SSRS is not using standard IIS, you need to follow custom steps below to bind SSL certificate to your Report Server
- Log in as Administrator.
- Open MMC and add the Certificates snap-in for the Local Computer (click File -> Add/Remove Snap-in -> Certificates -> Computer account -> Next -> Local computer -> Finish).
- Select Certificates (Local Computer) -> Personal -> Certificates.
- Right-click on the Personal Certificates for the Local Computer and select All Tasks -> Advanced Operations -> Create Custom Request.
- In the Certificate Enrollment wizard:
- Read the Before You Beginscreen and click Next.
- On the Select Enrollment Policy screen, under Custom Request, select Proceed without enrollment policy and click Next.
- On the Custom request screen:
- Template dropdown – “(No template) Legacy key” and leave “Suppress default extensions” unticked.
- Request format – PKCS#10.
- Click Next.
- On the Certificate Enrollment screen:
- click Details -> Properties. This will open a Certificate Properties window.
- On the Certificate Properties screen:
- General tab, enter a Friendly name (server/service name) and Description for your certificate.
- On the Subject tab
- Select Common Name from the Type menu, enter your fully qualified DNS (or DNS alias) name for the value, and click “Add”.
- Select Organization from the Type menu, enter your company name for the value, and click “Add”.
- Select State from the Type menu, enter your 2 letter state abbreviation for the value, and click “Add”.
- Select Country from the Type menu, enter your 2 letter country code (“US” if in the USA) for the value, and click “Add”.
- On the Extensions tab
- Expand “Key usage” and add “Digital signature” to the selected options
- verify “Make these key usages critical” is ticked
- Expand “Extended Key Usage (application policies)” and add “Server Authentication” and “Client Authentication” to the selected options
- verify that “Make the Extended Key Usage critical” is ticked
- On the Private Key tab
- Expand Cryptographic Service provider
- Remove “Microsoft Strong Cryptographic Provider (Signature)”
- Add “Microsoft RSA SChannel Crytographic Provider (Encryption)”.
- Expand Key Options -> Key size dropdown -> select 2048
- Select “Make private key exportable” to allow the exported certificate to be used on another host (clustered servers).
- Click OK.
- On the Certificate Information screen, click Next.
- Enter a file name for your CSR (e.g. certname.req)
- Select “Base 64” as the File Format.
- Click Finish.
Send this certificate request (certname.req) to your certificate authority team, they will generate a certificate for you and send the certificate back to you (in my case certificate.p7b) – which you can import via MMC into your personal store.
Once it is available in your server’s personal store, it will be visible under SSRS certificate binding screen.
If you are not able open directly in browser your PDF file stored in SharePoint document library and it is showing message box below, there is a way to tweak SharePoint for it.
The solution is to change Browser File Handling property on Web Application level. For that you need to be a Farm Administrator. Steps to change Browser File Handling property:
- Go to SharePoint 2010 Central Administration –> Application Management -> Manage Web Applications
- Select your web application and then click General Settings in the ribbon
- Scroll down to see Browser File Handling settings
- Select Permissive and click Ok
Then open your PowerShell on one of your SharePoint servers and execute following scripts to add mime type for PDF.
$webApp = Get-SPWebApplication http://intranet.domain
Go back and verify, now you will be able to open PDF files directly from your browser without saving it.
If you are new to ECM industry and would like to quickly deliver a roll up functionality for your contents, CQWP will be used to deliver this functionality.
Following MSDN links would be helpful to get-to-know about usage of this webpart.
If you are using default available site columns inside your content type, you are prone to errors (undocument issues) as described here in this post while referring columns into your XSL template https://www.nothingbutsharepoint.com/sites/devwiki/articles/Pages/Inconvenient-Content-Query-Web-Part-slots.aspx
Last but not the least, you will have to add additional markup, reformat the layout for XSL template and add header or footer to it – this post discuss it quite well on how to tweak XSLT http://blog.mastykarz.nl/wrapping-contents-content-query-web-part-additional-markup/
We are using SharePoint 2010 and we came across a situation where multiple upload feature is disabled for some of the users, on investigating further we identified that a series of settings are required both on server and client level. Though our users can upload single file at a time as shown below:
Server side settings
Following settings have to be ensured on SharePoint server to have this facitlity available to end users.
- Open Central Administration, Go to Manage web applications, select your web application where this feature needs to be enabled, click on Authentication providers from the top ribbon, click on your respective zone and then enable Client Integration as shown
- Open Central Administration, Go to Manage web applications, select your web application where this feature needs to be enabled, select General Settings from the top ribbon, enable Presence settings as shown below
Client side settings
Following settings has to ensured on client machine to use multiple upload feature
- Client should be having .NET Framework 3.5 installed on this machine
- Office 2010/2007 shouldn’t be installed before instaling .NET framework 3.5 as stated in first point
- In Internet explorer, specific add-on has to be enabled as shown below
(it is enabled by default, but just in case)
If all the above settings are ensured, your end users will be able to use multiple upload facility as it depends heavily upon client software installed.
The following pre-requisites needs to be ensured on client computer/laptop to enable multiple file upload functionality.
1) Windows XP and Office 2007
a. Upload multiple documents will work regardless of the order you install .NET (up to 3.5) and Office 2007
b. Upload multiple documents will NOT work without Office 2007 installed
c. Upload multiple documents WILL work even WITHOUT .NET installed, and only Office 2007 installed
2) Windows XP and Office 2010
a. Upload multiple documents will work ONLY if you install .NET up to version 3.5 BEFORE you install Office 2010
b. Upload multiple documents will NOT work without Office 2010 installed
c. Upload multiple documents will NOT work without .NET up to 3.5 (SP1) installed
3) Windows 7 and Office 2007
a. Upload multiple documents will always work in this situation, as long as Office 2007 is installed
4) Windows 7 and Office 2010
a. Upload multiple documents will always work in this situation, as long as Office 2010 is installed
i. Windows 7 ships with .NET 3.5 pre-installed, so you should never run into this issue
We are having SharePoint 2010 server farm and are using it for our LOB applications and corporate portal. Its being extensively used for collaboration among different teams and used as a document management solution lightly.
Being customers for Symantec in the region, we are using their product Enterprise Vault (EV) for archiving documents inside SharePoint 2010. Lately we came across a situation in which users aren’t able to download archived files from Intranet.
While opening PDF file, we were getting this error:
On opening MS-word file, we were getting following error:
On deeping dive further we found that for all SharePoint archived files, EV is appending stub into documents. After little search on the internet, issue became clear that documents stored inside SharePoint (over HTTPS) and archived via Symantec EV won’t be downloaded if you are using its product version 9.0 or before.
Following forums discussed the issues:
Further details for resolution can be found here at Symantec:
This issue will get resolved once we upgrade to Symante EV product version 9.0.3 as it was the limitation in earlier version when items were being accessed via HTTPS.
When you install SharePoint farm in your environment the only connection between your organization’s license type and license key used during installation of the farm is activation of either Standard or Enterprise features.
The thing is that the only supported change is changing from Standard to Enterprise. There is no supported way of changing from one standard key to another standard key or from one enterprise key to another enterprise key and you can’t downgrade from enterprise to standard. The only supported way is to re-install again!
So folks, please use license key carefully when required as you will loose the option to change it later on after installation.