First thing is to download files for the correct edition SQL server - as many resources indicate it works for Express edition unless you have download the one with Advance Services.
I downloaded from
http://www.microsoft.com/express/Database/InstallOptions.aspx
which is the only Express version that contains Full-Text Search.
Second, find the right sample database file. In my case, I have Windows 7 and SQL Server 2008 R2 Express (installed via Web platform installer3.0), and SQL server 2008 R2 Express with Advance Services (installed from the download .exe file). I downloaded "AdventureWorks2008R2_SR1.exe" sample database from http://msftdbprodsamples.codeplex.com/releases/view/55926
Notes**I had the SQL server 2008 Express installed on my computer. The first time of installing of SQL 2k8 R2 Express with Advance Services was "successfully completed" but not right because the Full-text services option (required) was missing. I uninstalled all my SQL server 2008 components through the control panel. And then tried to install only "SQL 2k8 R2 Express with Advance Services" edition but the installation aborted. I was guessing I removed too more components than needed. so I decided to install the SQL Server 2008 Express through the web platform installer to avoid any missing dependency.
The installation of SQL 2k8 R2 Express with Advance Services finally proceed and completed. I was able to find the options of Full-text Search service and started it. I was able to find the FileStream option and enabled it. Everything looks good.
Here came the installation of the most wanted part-sample databases. A self-extracting file and the process went smooth and have no problem at all. below are the screen shots:
Wednesday, April 27, 2011
Wednesday, March 16, 2011
Windows Authentication using local developer server
I'm developing an ASP.NET application which needs Windows Authentication. I have the web.config set up to deny anonymous users and use Windows mode for authentication, but my local development version still lets me pass right through to the site. In order to test different user set-ups, I need to force authorization so I can change users.
How do I set up my system (config files, VS2005 settings, IIS, etc?) to force the authorization window to popup on the site when I'm running on local asp.net development server? In other words, how do I get the authentication popup when running the site in Debug mode?
You will also need to configure IIS and have your application point to IIS instead of the local web server
To configure your application to point to IIS
How do I set up my system (config files, VS2005 settings, IIS, etc?) to force the authorization window to popup on the site when I'm running on local asp.net development server? In other words, how do I get the authentication popup when running the site in Debug mode?
You will also need to configure IIS and have your application point to IIS instead of the local web server
To configure Windows authenticationhttp://msdn.microsoft.com/en-us/library/ms998358.aspx
- Start Internet Information Services (IIS).
- Right-click your application's virtual directory, and then click Properties.
- Click the Directory Security tab.
- Under Anonymous access and authentication control, click Edit.
- Make sure the Anonymous access check box is not selected and that Integrated Windows > authentication is the only selected check box.
To configure your application to point to IIS
- Right click on your web project, and then click Properties
- Click the Web tab
- Click the "Use Local IIS Web Server" radio button
Things on the Development server
- A web server
- A script to migrate from dev to test
- A script to migrate test to production
- a script to backup your svn to S3 or similar offsite backup storage
- a good text editor
- sed, awk and ruby for the really hard scripts
- postmortem debugging tools, for Windows that is:
- umdh (for memory leaks)
- drwtsn32 (for crashes),
- cdb (to get minidumps from hung apps),
- windbg (to inspect the minidumps).
set up a team development testing environment
Ideal for Microsoft Technologies is TFS (Team Foundation Server), which has all the features you want.
In case you don't want TFS, try this:
Version control system
Bug Database / Project Management / Tasks
Developers environment
Development machine: Visual Studio + VisualSVN/TortoiseSVN + Resharper
Buildserver: Teamcity
LAN testing server: Webserver with build by buildserver + DB with daily copy of live
QA/Staging depends on the project size.
In case you don't want TFS, try this:
Version control system
Bug Database / Project Management / Tasks
Developers environment
- Dual screen
- Powerful PC
- Quality chair
- Whiteboard
- Free coffee
Development machine: Visual Studio + VisualSVN/TortoiseSVN + Resharper
Buildserver: Teamcity
LAN testing server: Webserver with build by buildserver + DB with daily copy of live
QA/Staging depends on the project size.
Monday, March 14, 2011
Web deployment info website
http://vishaljoshi.blogspot.com/2009/09/overview-post-for-web-deployment-in-vs.html
http://stackoverflow.com/
http://code.msdn.microsoft.com/site/search?f%5B0%5D.Type=ProgrammingLanguage&f%5B0%5D.Value=C%23&f%5B0%5D.Text=C%23&f%5B1%5D.Type=Platform&f%5B1%5D.Value=Web&f%5B1%5D.Text=Web&f%5B2%5D.Type=VisualStudioVersion&f%5B2%5D.Value=10.0
http://stackoverflow.com/
http://code.msdn.microsoft.com/site/search?f%5B0%5D.Type=ProgrammingLanguage&f%5B0%5D.Value=C%23&f%5B0%5D.Text=C%23&f%5B1%5D.Type=Platform&f%5B1%5D.Value=Web&f%5B1%5D.Text=Web&f%5B2%5D.Type=VisualStudioVersion&f%5B2%5D.Value=10.0
Friday, March 4, 2011
Install IIS WMSvc
The default IIS 7 installation options do not include the Management Service (also referred to as the Web Management Service (WMSVC)), which is required for remote administration. If you have not installed the Management Service, follow the steps in this procedure to install it.
To install the Management Service:
- Click Start, type Server Manager in the Search box, and press ENTER to open Server Manager.
- In the tree, under Roles, select Web Server (IIS).
- Click Add role services, and then select Management Service as shown in the image below.
- Click Next and follow the instructions to complete the installation.
Publishing your website to a remote server
"I have always felt that publishing a site so it works on your remote server is a little bit of a black art. Many stars have to align:
"
- Files and databases have to transfer
- Settings such as connection strings have to transform to remote values
- Remote server has to be configured properly e.g. must have all dependencies installed
Error: “The application pool that you are trying to use has the 'managedRuntimeVersion' property set to 'v2.0'. This application requires 'v4.0'.”
Solution: An application pool provides isolation for websites. Typically, web hosting providers create one application pool per website, and set default values for a number of attributes. One of these attributes is the version of the .NET framework. The user can often change this value between .NET 2.0 and .NET 4.0 through the web hosting provider’s control panel. You will see this error during publishing if you are publishing an ASP.NET Web Pages application, which requires .NET 4.0, to a hoster who has given you a website with a .NET 2.0 application pool. Similarly, you will see this error if you are publishing an application that requires .NET 2.0 to a website associated with an .NET 4.0 application pool. The solution is to set the .NET framework version in the web hosting provider’s control panel or, if there are no compatibility issues, change your application’s .NET framework version in WebMatrix’s Settings workspace.Error: “Username or password incorrect” error when using Web Deploy
Solution: This is probably because the value in Site Name is incorrect. Site Name must contain the name of the IIS site on the remote server. Typically, it matches your domain name, but it doesn’t have to. For example, it can be “Default Web Site” (if you have a dedicated server) or “foo” or “foo.com”. Web Deploy must authenticate to the site before it can execute any providers.Error: Web management service not started on destination
Solution: You may see this error if you are deploying to a server you have set up yourself. Web Deploy requires a service called Web Management Service (wmsvc) to be running on the remote server. You can get this error if the service is not started. This blog post is a good starting point to learn how to configure a remote server with Web Deploy and wmsvc.Error: Failed to invoke provider “iisApp”
Solution: Under the covers, WebMatrix users Web Deploy’s iisApp provider to sync files and directories, and to mark folders as applications. You may see this error if delegation rules are not configured correctly on the remote server. Delegation rules allow the user to execute some actions that require administrative privileges, such as marking a folder as an application. This blog post and this one gives good information on how to configure delegation rules.Error: Bad gateway: check proxy settings
Solution: This one is literally what it says – check proxy settings because Web Deploy traffic is being blocked. Try installing your corporation’s required firewall client, and disabling all settings in Internet Explorer > Tools > Options > Connections > LAN settings."
Wednesday, March 2, 2011
Breadcumb links for web
Use JavaScript to read where your page is in the site folder structure and build back links to the pages higher up in the hierarchy. If you're trying to add breadcrumb links to PHP pages, you might try our PHP breadcumb links script instead.
Download the .zip archive of the script from: MPBackLinks.js
There are a few variables near the top of the MPBackLinks.js file that you can also customize to better control the appearance and behavior.
Using the Script in HTML
You can customize the styling of your menu using CSS. The menu is created inside a
Download the .zip archive of the script from: MPBackLinks.js
There are a few variables near the top of the MPBackLinks.js file that you can also customize to better control the appearance and behavior.
Using the Script in HTML
<script type="text/javascript" src="MPBackLinks.js"></script>
You can customize the styling of your menu using CSS. The menu is created inside a
with a class assigned named "mp_backlinks". You can create a new CSS class sytle named "mp_backlinks" and assign whatever style settings you want.
Tuesday, February 8, 2011
Set up an AD (basic)
I may not set up a AD but it is good to know the basic how.
"I shall provide you the easiest steps which I am following in setting up of an active directory based domain at my office.
1. Install a Windows Server Machine
2. Run DCPROMO on it from command prompt and configure it as the primary DC and while asked configure DNS also on the same machine. Now the important things you should remeber to configure every systems in to a domain are DC FQDN, IP address of DC, an Administrator Username and Administrative password
3. Just connect every computers including server just configured to a switch in star topology
4. In every client computers give IP address in the same range as the DC and use the preferred DNS IP address as that of the IP address of DC
5. Go to My Computer-->Properties-->Computer Name-->Network ID on every client computers and join each one in to domain by following the steps.
6. Restart each computer and now the clients are ready as the member of a domain group
7. You may go to Active Directory Users and Computers in DC and can add user names of each users to grant them network acess on each computer
8. Remember to create general username and password on each machines as each users may try to login to another computers to acess shares, printers etc."
"QQ:
"I shall provide you the easiest steps which I am following in setting up of an active directory based domain at my office.
1. Install a Windows Server Machine
2. Run DCPROMO on it from command prompt and configure it as the primary DC and while asked configure DNS also on the same machine. Now the important things you should remeber to configure every systems in to a domain are DC FQDN, IP address of DC, an Administrator Username and Administrative password
3. Just connect every computers including server just configured to a switch in star topology
4. In every client computers give IP address in the same range as the DC and use the preferred DNS IP address as that of the IP address of DC
5. Go to My Computer-->Properties-->Computer Name-->Network ID on every client computers and join each one in to domain by following the steps.
6. Restart each computer and now the clients are ready as the member of a domain group
7. You may go to Active Directory Users and Computers in DC and can add user names of each users to grant them network acess on each computer
8. Remember to create general username and password on each machines as each users may try to login to another computers to acess shares, printers etc."
"QQ:
First off, I would like to thank all who have responded so far...
I have a couple of questions, but best I should let on one more detail of our setup. I run a separate box as a router/gateway, installed with Untangle. This box is set to 192.168.1.1, and provides gateway access to the outside world.
The server is assigned 192.168.1.3 (192.168.1.2 is assigned to an unused DMZ port on the Untangle server).
Now what I am particularly fuzzy on is what to assign the would-be DC server as regards a being a "domain controller for a new domain" as well as "domain in a new forest". Are these options correct in my situation? What do I assign the DNS name as, or does it matter? Keep in mind, this server is not meant to be accessed from the internet, so I am unclear as to the subtleties of setting up INTERNAL domains...does it matter what I call this?
Also, as above the netbios name?
I am also fuzzy in the setup of DNS in my particular case. I have the internal network all static IP's (192.168.1.x), and like I mention have a separate gateway/router system, how do I set this up?
One of the walkthroughs posted in this thread are instruction for a laboratory environment, and recommend leaving password empty for directory services restore mode, should I do this?
Anyway, the initial setup is what I am worried about. I feel pretty comfortable setting up users and permissions, as well as playing with the group policies...
I have a couple of questions, but best I should let on one more detail of our setup. I run a separate box as a router/gateway, installed with Untangle. This box is set to 192.168.1.1, and provides gateway access to the outside world.
The server is assigned 192.168.1.3 (192.168.1.2 is assigned to an unused DMZ port on the Untangle server).
Now what I am particularly fuzzy on is what to assign the would-be DC server as regards a being a "domain controller for a new domain" as well as "domain in a new forest". Are these options correct in my situation? What do I assign the DNS name as, or does it matter? Keep in mind, this server is not meant to be accessed from the internet, so I am unclear as to the subtleties of setting up INTERNAL domains...does it matter what I call this?
Also, as above the netbios name?
I am also fuzzy in the setup of DNS in my particular case. I have the internal network all static IP's (192.168.1.x), and like I mention have a separate gateway/router system, how do I set this up?
One of the walkthroughs posted in this thread are instruction for a laboratory environment, and recommend leaving password empty for directory services restore mode, should I do this?
Anyway, the initial setup is what I am worried about. I feel pretty comfortable setting up users and permissions, as well as playing with the group policies...
AA:yes, your first dc should be domain controller for new domain and domain in a new forest. ad isn't affected by the IP addressing scheme though you are likely going to want outbound internet connection for things like updates unless you are using a WSUS server or some other product. you may also want to allow ntp out so your DC can sync with an internet time source unless your router will be the intermediary.
the domain name, dns name, and netbios name are also arbitrary as long as they are unique within your network (which i'd assume they will be). the only recommendations that i have here are:
1. once you put in the domain name, take the defaults everywhere else. that is, use the short name that ad presents to you and don't change the dns namespace. that is only going to lead to headaches.
2. don't use a single label domain name for the dns name (eg internal.). this is guaranteed to be a pain for you.
3. don't use a .lcl extension for your dns or domain name (eg internal.lcl). though msft products are fine with it, there are 3rd-party products that are not.
you can leave the dsrm password blank if you'd like. it certainly isn't recommended and it does create some minor level of risk. "
the domain name, dns name, and netbios name are also arbitrary as long as they are unique within your network (which i'd assume they will be). the only recommendations that i have here are:
1. once you put in the domain name, take the defaults everywhere else. that is, use the short name that ad presents to you and don't change the dns namespace. that is only going to lead to headaches.
2. don't use a single label domain name for the dns name (eg internal.). this is guaranteed to be a pain for you.
3. don't use a .lcl extension for your dns or domain name (eg internal.lcl). though msft products are fine with it, there are 3rd-party products that are not.
you can leave the dsrm password blank if you'd like. it certainly isn't recommended and it does create some minor level of risk. "
Wednesday, January 12, 2011
How to do print screen in Mac OS X
Here are few ways to do screen capture in Mac OS X.
1.
1.
- Switch to the screen that you wan to to do screen capture
- Hold down Apple key ⌘ + Shift + 3 and release all
- then use your mouse to click on the screen
- Done. You will see a picture file in at your desktop. That’s the screen capture picture.
- Switch to the screen that you wan to to do screen capture
- Hold down Apple key ⌘ + Shift + 4 and release all key
- Now, You will see the mouse cursor will change to +
- You can start to drag your mouse to select the portion you wish to capture.
- Once finish, you will see a picture file in at your desktop. That’s the screen capture picture!
- Switch to the screen that you wan to to do screen capture
- Hold down Apple key ⌘ + Shift + 4 and release all key
- Now, You will see the mouse cursor will change to +
- Press the space bar once
- You will see the mouse cursor change to a camera
- Now you can use the camera to select which application window to screen capture
- Once finish, you will see a picture file in at your desktop. That’s the screen capture picture!
Subscribe to:
Posts (Atom)