Visual Studio 2008

At its TechEd 2007 conference here, Microsoft announced June 4 that the next version of Visual Studio, which has been known by the code name "Orcas," has been dubbed Visual Studio 2008.
In addition, C. Joe Marini, group product manager of developer marketing at Microsoft, said beta 2 of Visual Studio 2008 will become available later this summer and will include a new feature known as the Visual Studio Shell. The Visual Studio Shell enables developers to create and distribute their own custom tools built on top of the Visual Studio IDE (integrated development environment).
"Partners and developers want a way to build their developer tool products on top of Visual Studio as a starting point so they can use the Visual Studio base technologies and services," Martini said in an interview with eWEEK.
The Visual Studio Shell will operate in two different modes. The first is the Integrated Mode, which is for developers creating programming language integration with Visual Studio, Marini said. The second is known as Isolated Mode and is for Microsoft partners and customers who want to take the base technology of Visual Studio and custom brand it, he said.

Visual Studio 2008 is interesting on several levels. First and I think this is very significant is that it works with .NET 2.0 and you can build applications that run on .NET 2.0. This means it’s possible to take advantage of many of the new features in Visual Studio - especially the new designer and the somewhat improved JavaScript support - even for today’s projects. That makes the new tool very palatable to try and play with immediately. I’ve moved several of my internal applications to Orcas and it’s been a pleasure working in VS 2008.

One of the biggest advantages in VS 2008 is the new HTML editor both for markup and design view. It’s based on the same editor that’s in Microsoft Web Expression (which is a great tool BTW and which I use daily!) and provides a ton of improved functionality and much better rendering. However, the biggest bonus that you’ll notice immediately with the new editor is that it is much, much faster than the VS 2005 editor. You know the feeling in VS 2005 as you open a markup or worse a designer page and you wait and wait and wait some more. With VS 2008 that is no longer the case - activating markup or design view happens in a second or two even for complex pages. Not only that but because there’s split view for design and markup you rarely switch views and because both panes stay in sync the whole experience is much more expressive. The editor and speed alone is a big productivity improvement at least for me.

It’s important to remember that the ASP.NET team has already delivered very important support features prior to the Orcas release cycle. Specifically I’m thinking of ASP.NET AJAX and full support for the IIS 7 integrated pipeline, which in my opinion really counts as the ASP.NET 3.0!

Futures

Then there’s also the ASP.NET Futures features, which at this point are still up in the air. Some of the Futures features have been getting kind of stale like the AJAX features that were originally introduced in the ATLAS days. The advanced libraries like effects, drag and drop, basic control features, databinding and JsonConverters haven’t been updated since ASP.NET AJAX 1.0 was released which is a bummer. I maintain that ASP.NET AJAX’s client library is what amounts to an incomplete product and Microsoft should really finish that part of the framework. The Futures features at least bring the library on par with some much smaller JavaScript libraries. Effects functionality and more high level DOM support are supported by just about all JS libraries to date but the ASP.NET AJAX Client library is very light on any sort of client support. Unfortunately it looks like there won’t be much of a change for the Orcas release .
The Futures release also contains a bunch of new functionality that relates to Silverlight and embedding Silverlight and XAML content into pages. Silverlight is getting all the dibs these days and it’s likely that this stuff will find its way into the new runtimes. There are a few other odds and ends in the Futures release such as Rails like dynamic framework that provides rough scaffolding for a database.

It’s unclear at this point what Futures features will make it into the final runtimes as Microsoft is still working out the details of these items at this time

How to retrive the images from Databaase?

this code is used to store the images in database usign stored procedures and this code also proved practically proved

1. go to sqlserver then
create table InsertPhoto(eid int identity(1,1),ename varchar(30),photo image)then excute it
after that write procedues in sql serever only

we should write like that

CREATE PROCEDURE sp_InsertPhoto(@ename varchar(30),@photoclip_IM image )ASINSERT INTO insertphoto ( ename,photo )VALUES ( @ename,@photoclip_IM )GO

then excute it sqlsever only

after that go to asp.net page

go to html controles

in that
take input(file) drop on the asp.net page

go to html source page make it runat="server" beside input file control and then

in that control only we should take input (submit) button

drop on the page

we should include this namespaces

using System.Data.OleDb;
using System.Drawing.Imaging ;
using System.IO;using System.Drawing;

in submit button_click event we write like this

Stream imagestreame = File1.PostedFile.InputStream;
int len = File1.PostedFile.ContentLength;
byte[] imagecontent = new byte[len];
imagestreame.Read(imagecontent, 0, len);

if (cn.State == ConnectionState.Closed)
{ cn.Open();
}
cmd=new OleDbCommand ("sp_InsertPhoto",cn);
cmd.CommandType = CommandType.StoredProcedure;
OleDbParameter pr = new OleDbParameter("@ename", OleDbType.VarChar);

pr.Value = File1.Value;
cmd.Parameters.Add(pr);
OleDbParameter primage = new OleDbParameter("@photoclip_IM", SqlDbType.Image );
primage .Value= imagecontent;
cmd.Parameters.Add(primage);
cmd.ExecuteNonQuery();
Response.Write("image stored");
}}

for retriving the same image from database we should write like this
you must include this name spaces

using System.Data.OleDb;
using System.Drawing.Imaging ;
using System.IO;using System.Drawing;

in button_click event
OleDbDataAdapter adp=new OleDbDataAdapter ();
DataSet ds=new DataSet ();
int i=0;
try{

cn .Open();cmd=new OleDbCommand ("select photo from insertphoto where eid=1",cn);

adp.SelectCommand =cmd ;
ds=new DataSet("st");
adp.Fill(ds);
byte [] bits= (byte [])(ds.Tables[0].Rows[i][0]);
//converting the data to byteMemoryStream memorybits= new MemoryStream(bits);
Bitmap bitm =new Bitmap(memorybits);
Response.BinaryWrite(bits);}catch(Exception ex){Response.Write(ex.Message);
}
finally
{
cn.Close();
}
}

}
}

Search engine optimization (SEO)

Search Engine Optimization [SEO]

is the process of improving the volume and quality of traffic to a web site from search engines via "natural" ("organic" or "algorithmic") search results. Usually, the earlier a site is presented in the search results, or the higher it "ranks", the more searchers will visit that site. SEO can also target different kinds of search, including image search, local search, and industry-specific vertical search engines.

As a marketing strategy for increasing a site's relevance, SEO considers how search algorithms work and what people search for. SEO efforts may involve a site's coding, presentation, and structure, as well as fixing problems that could prevent search engine indexing programs from fully spidering a site. Other, more noticeable efforts may include adding unique content to a site, ensuring that content is easily indexed by search engine robots, and making the site more appealing to users. Another class of techniques, known as "Black Hat" SEO or spamdexing, use methods such as link farms and keyword stuffing that tend to harm search engine user experience. Search engines look for sites that employ these techniques and may remove their listings.

The initialism "SEO" can also refer to "search engine optimizers", a term adopted by an industry of consultants who carry out optimization projects on behalf of clients, and by employees who perform SEO services in-house. Search engine optimizers may offer SEO as a stand-alone service or as a part of a broader marketing campaign. Because effective SEO may require changes to the HTML source code of a site, SEO tactics may be incorporated into web site development and design. The term "search engine friendly" may be used to describe web site designs, menus, content management systems and shopping carts that are easy to optimize.