ChandrasekharRao.D

Create SVN Repository

Creating Svn Repository
Step:1  Download tortoise svn  --> https://tortoisesvn.net/downloads.html
Step2:    Download subversion -->  https://sourceforge.net/projects/win32svn/
Step3:   Install tortoise svn .
Creating svn repository through command prompt.
Step:4  open command prompt Run as administrator. (Follow below guidelines)

If you want to create only one repository you may create only one  only the above am creating three repositories .
Creating svn repository through GUI
create newfolder(anyname)  any location  on your pc -->right click-->tortoise svn -->createrepositoryhere-->ok
Ex: c:/users/chandu/desktop/svnrepository
      Repository created.
Installing SVN service to our pc for accessing through svn protocall
Step:5  Install subversion to PC
Step6:
If you would like to just cut and paste that command, here it is:
sc create svnserve binpath= "\"C:\Program Files (x86)\Subversion\bin\svnserve.exe\" --service -r C:\SVNRepository" displayname= "Subversion Server" depend= Tcpip start= auto .
Let me break down the elements in the command and explain them in more detail.
1. sc create svnserve:
command says that we are creating a service and that we want to give it an identifier of “svnserve”. You could use a different identifier if you prefer. The only time this name will matter is if you want to manage the service from the command line. For example the command “net start svnserve” can be used to start the service. In that example, the service identified by the name “svnserve” would be started.
2. binpath= "\"C:\Program Files\CollabNet Subversion Server\svnserve.exe\" --service -r C:\repositories"
It is telling Windows the name of the program to run when it starts the service as well as the arguments. Notice that there is some funky usage of double-quotes and escaping. Since the parameter value has spaces, the whole thing needs to be enclosed in double-quotes. In addition, since the path to the svnserve executable contains spaces, it also needs to be enclosed with double-quotes. However, since those double-quotes are inside of another set, they need to be escaped. So be sure to enter the command exactly as shown.
3.      You have to include the --service option as an argument as that is what tells svnserve to respond to the Windows service life cycle events. You must NOT include any conflicting options such as --daemon (-d), --tunnel, or --inetd (-i). You can include additional options such as the -r option shown above. If you want to change the default port, you would want to include the --listen-port NNNN option as an argument.
4.  displayname= "Subversion Server"
This value allows you to specify the name you will see for the service when working with the Services GUI in Windows. If you have embedded spaces in the name, be sure to enclose it all in double quotes as shown.
depend= Tcpip
This value configures the service so that Windows does not attempt to start it until the TCP/IP service has started.
start= auto
This value configures the service to start automatically when Windows starts.
Now that we have added the service, we could start it by running the command:
net start svnserve
Instead, let’s view the service in the Windows GUI and start it from there. The location of the Services application has moved around in various versions of Windows. It is generally available in the Administration Tools folder with the name “Services.”
Step:7  windows button -->services
Step:8 Test The server
Open the Windows command prompt and run the svn info command to verify that we can connect to the server.
In this example, I used the svn info command and gave it the URL to the repository I created and named “dev”. Note that the repository name is exposed in the URL, but not the on disk location (C:\repositories). I can access different repositories just by using a slightly different URL. The three repositories I created at the beginning would be accessed via these URL’s:
If you were running these commands from a different machine, you would need to specify the IP address or name of the server in place of localhost. If you used a different port than the default, by using the --listen-port option on the svnserve command, then you would need to include the port number in the URL:
svn://localhost:3691/dev
step: 9  we have svn repository location
url -:  svn://<portNumber>(or) (pc-name)/<svn repositoryname>
Ex:svn://192.168.1.117/dev
Step :10 Here we can add existing or newly created project folder
Open repository location  Ex: c:/users/chandu/desktop/svnrepository then right click-->repo browser
Here appear on window -->right click -->add newfolder--> add here existing folder
Step:11  open  any browser
Enter url svn://localhost/dev -->enter -->choose svnclient-->ok
Here you can see added folder so you can check out eclipse these project with in network.



If You encounter a connection timed out error while you are trying to  connect from remote desktop.
You need to do the following steps.
Step 1: You need to check that  listening port of svn server is open or not . If not you should open that port .
We tested this approach so you can  follow this.
Step2 : In order to  see that  port is open or not in cmd prompt type the following command netstat -an
            In  this list you can find the port numbers which are listening.
Step 3: TO Open Port number  on which svn server is running you have type the following command on Cmd prompt.       

netsh advfirewall firewall add rule name="Open Port 3690" dir=in      action=allow   protocol=TCP localport=3690
The Following Link Will give the details explanation about how to add port number through command prompt.

Another way is to open port number is : Follow the below link - we didn’t tested this one.
Author : Chandu

Internet vs intranet



Internet

  • Internet is wide network of computers and is open for all.
  • Internet itself contains a large number of intranets.
  • The number of users who use internet is Unlimited.
  • The Visitors traffic is unlimited.
  • Internet contains different source of information and is available for all.
  • Internet uses the standard Internet Protocol (TCP/IP)
  • Every computer in internet is identified by a unique IP address.
  • IP Address is a unique set of numbers (such as 110.22.33.114) which identifies a computer’s location.
  • A special computer DNS (Domain Name Server) is used to give name to the IP Address so that user can locate a computer by a name.
  • Internet is accessible to every user all over the world.

Intranet

  • Intranet is also a network of computers designed for a specific group of users.
  • Intranet can be accessed from Internet but with restrictions.
  • The number of users is limited.
  • The traffic allowed is also limited.
  • Intranet contains only specific group information.
  • Usually each company or organization has their own Intranet network and members/employees of that company can access the computers in their intranet.
  • Each computer in Intranet is also identified by an IP Address which is unique among the computers in that Intranet.


Similarities in Internet and Intranet
  • Intranet uses the internet protocols such as TCP/IP and FTP.

  • Intranet sites are accessible via web browser in similar way as websites in internet. But only members of Intranet network can access intranet hosted sites.

  • In Intranet, own instant messengers can be used as similar to yahoo messenger/ gtalk over the internet.

Differences in Internet and Intranet

  • Internet is general to PCs all over the world whereas Intranet is specific to few PCs.

  • Internet has wider access and provides a better access to websites to large population whereas Intranet is restricted.

  • Internet is not as safe as Intranet, as Intranet can be safely privatized as per the need.

Desktop vs Web Application



What is the difference between the web application and desktop application?

The main difference between the Web based application and Window based application
is that the Web application can be access from anywhere in the world through the internet
whereas window based application need to be install on your machine to access.


Web applications run on web servers (usually IIS)
Winforms Applications run on Clients


Web Application Advantages

The biggest, and most obvious, advantage to using a web application is flexibility. A web application can be accessed from any computer no matter where you are. This is due to the fact that a web application only exists online.

Of course, constant accessibility depends on your current Internet connection.

Desktop Application Advantages
Desktop applications are reliable and trustworthy. You can access a desktop app as long as you have your computer within reach. These applications don’t rely on an Internet connection in most instances.

One unfortunate drawback to a desktop application is that you can’t access this type of app if you don’t have your computer handy.

Further Web Application Disadvantages
Safety and security is a huge problem when it comes to web applications. Since the Internet is not a secure place, any business conducted online is at risk for a security breach. This is also true when it comes to Intranet.

Web applications are slower than desktop applications. This is largely due to the fact that various web app sites gain heavy traffic on a frequent basis. Avoiding a slow web app is difficult to do, since users do not directly control these applications.

The Future of Apps
There’s no doubt that web applications serve some very interesting purposes. As more and more people gravitate towards web apps, desktop apps may become obsolete. Then again, the problems that web apps have (security, accessibility) are large ones. For this reason, desktop applications have not been wipe out completely.

In the end, all applications are simply programs, and programs contain errors.

Web applications are mostly physical 3 tier application

Client (the webbrowser), The middle Tier (the webapplication) The server
(the database).
Physical is a window form application mostly a 2 tier, although in a good
design it has multi layers (what is by some called tiers).
Client (the window forms) The server (the database).

- web applications have the authentication/authorization mechanism partially
built
- desktop applications (windows forms) need the entire mechanism built
- web apps have validation controls
- windows apps don't have validation controls, data needs to be validated
through code