asp.net upc-a

asp.net upc-a

asp.net upc-a

asp.net upc-a

asp.net upc-a

asp.net upc-a,

asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,

asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,

asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,
asp.net upc-a,

Ruby is an interpreted language, so to distribute Ruby programs you can simply distribute the source code files you ve written. Anyone else who has Ruby installed can then run the files in the same way that you do. This process of distributing the actual source code for a program is typically how most programs developed using a scripting language, such as Ruby, are shared; but more traditionally, software has been distributed without the source code included. Popular desktop application development languages such as C and C++ are compiled languages whose source code is converted directly into machine code that runs on a certain platform. This software can be distributed by copying the resulting compiled machine code files, rather than the source, from machine to machine. However, this technique is not possible with Ruby, as there is currently no Ruby compiler available (with the exception of that in JRuby, but this is still a nascent area), so you have to distribute your source code in one sense or another for other people to be able to run your programs.

Note Later in this chapter, we ll look at making the functionality of your Ruby programs available across a

Note You can also define your own transformation matrix, if you need to modify or combine the four transformation types. See Pro Silverlight 2 by Matthew MacDonald (Apress, 2008) for details on how to do this.

network. This technique does not require you to make your source code available, although it does require you to maintain a running copy of your program on a machine that s network accessible (such as a web server).

Now you should be in a position to test what data is exposed to each user. You can do this in the SQL Server Modeling Command Prompt window by impersonating a user with the runas command. Bring up the SQL Server Command Prompt window, and execute the following code: runas /user:CarQC "sqlcmd.exe /y25" The /y25 switch on the sqlcmd.exe command is required, and sets the display width for the SQLCMD prompt window. The system will prompt for the CarQC user s password, which should be the same as the user name (see Figure 7-51). After that is accepted, a separate SQLCMD window will appear, where you can run SQL queries as the CarQC user against the MfgComponents view.

To see how you can distribute Ruby source code, let s take an example Ruby file and call it test.rb: puts "Your program works!" If you copy test.rb to another computer that has the Ruby interpreter installed on it, you can run the program directly with the Ruby interpreter as you would normally: ruby test.rb

Your program works! This technique works well if you re passing programs between your own machines or servers, or if you re distributing your programs to other developers. As long as the other users and machines have the same Ruby libraries or gems that your program uses, your program should run fine. For example, if you develop something to work with the standard version of Ruby that comes with Mac OS X, your program should work just fine on other Mac OS X machines (assuming they are running the same or a later version of OS X that includes Ruby). This ability to interpret the code in the same way on varying machines is one benefit of interpreted languages over compiled languages. If the same version of the Ruby interpreter is available on a different platform, it should run the same programs that your Ruby interpreter does. With compiled code (code that is specifically compiled down to machine code for a specific platform), it is not the case that it will run identically on all platforms; in fact, it usually won t! What if you want to distribute your Ruby program to people who aren t au fait with the Ruby interpreter Depending on the target operating system (that is, the operating system the user is running), there are several ways to make deploying Ruby applications simpler.

Figure 10-16 shows a Silverlight 2 application that has been divided into four grid cells. Each cell contains two rectangles that have their width and height set to 100 pixels. One

On Unix-related operating systems (Linux, OS X, BSD, and so on), you can engineer your program to run more simply by using a shebang line.

Windows. You can use shebang lines such as #!ruby and #!c:\ruby\bin\ruby.exe to make Ruby CGI scripts work under Apache on Windows.

For example, say your script were to look like this: #!/usr/bin/ruby puts "Your program works!" Unix-related operating systems support putting the name of the interpreter of a file on the first line of the file with a shebang line, where the shebang is simply the pound (#) sign and the exclamation mark (!).