LE, the container format already in use in Windows applications to allow objects and documents to communicate with each other and share information. Blackbird documents would be stored in what was called Blackbird Data Format (BDF), a structured format based on OLE storage. An SGML-based markup language, Blackbird Markup Language (BML), was also created to help automate the creation of documents, though documents based on markup would be processed into the native data format to be used as OLE objects, so would suffer performance disadvantages. To give developers more flexibility, Microsoft planned to include a utility that would allow conversion between BDF and BML, as well as HTML, in any direction.

Additionally, there would be an application resource installer that packaged custom fonts, OLE controls, and other resource files for a Blackbird application. The package would download when a user activated the application for the first time, or otherwise to update the package already on a user's system. Microsoft also advertised that Blackbird would take advantage of features within Windows 95 like shortcuts, and would allow the user to automatically schedule the delivery of content.

There were three components to the platform —  an authoring system called the Blackbird Designer, a visual drag-and drop environment similar to that included with Visual Basic; the Blackbird Server, which ran on Windows NT; and the Blackbird Client, a runtime module to lets users access and run Blackbird applications. URLs for Blackbird applications were OLE monikers.

Microsoft argued that Blackbird development would be cross-platform, since OLE support had already existed on Macintosh and there was work in progress on porting it to Unix systems. To guarantee security, the company planned to act as a certifying authority for OLE controls (OCXs), and encourage third parties to be certifying authorities.

Project history

Blackbird was announced in March 1995 as part of the upcoming Microsoft Network, and by August, it had been clear that Microsoft intended it to run more widely over Internet protocols. The technology was later demonstrated on MSN and Microsoft released a beta version of the developer tools, but by the end of 1996, when plans for a new version were announced, the designer then renamed to "Visual Studio", they disclosed they would not use the proprietary Blackbird file formats, but rather, standard HTML. It soon became clear the original project was effectively scrapped, and the designer later became Visual InterDev, a general web content creation tool for creating
LE, the container format already in use in Windows applications to allow objects and document to convey with each other and share information. new world blackbird documents would be stored in what was called Blackbird Data Format (BDF), a integrated format base on OLE storage. An SGML - based markup language, Blackbird Markup Language (BML), was besides created to help automate the creation of document, though documents based on markup would be processed into the native data format to be used as OLE object, so would suffer performance disadvantage. To give developers more tractability, Microsoft planned to admit a utility that would allow conversion between BDF and BML, as well as HTML, in any direction. 

 Additionally, there would be an application resource installer that packaged customs fonts, OLE controls, and other resource files for a Blackbird application. The package would download when a exploiter activated the application for the first time, or otherwise to update the package already on a user's system. Microsoft also advertised that Blackbird would consider advantage of features within Windows 95 like shortcuts, and would allow the exploiter to automatically schedule the delivery of content. 

 There constitute three components to the platform —   an authoring system call the Blackbird Designer, a visual drag - and drop environment similar to that included with Visual Basic; the Blackbird Server, which ran on Windows NT; and the Blackbird Client, a runtime faculty to lets users access and run Blackbird applications. URLs for Blackbird applications were OLE monikers. 

 Microsoft argue that Blackbird development would be cross - platform, since OLE support had already existed on Macintosh and there was workplace in progress on porting it to Unix systems. To undertake security, the party planned to act as a certify authority for OLE control (OCXs), and encourage third party to be certifying government. 

 Project history 

 Blackbird was announced in March 1995 as contribution of the upcoming Microsoft Network, and by August, it had been absolved that Microsoft intended it to run more widely over Internet protocols. The technology was by and by demonstrated on MSN and Microsoft released a beta version of the developer tools, but by the end of 1996, when plans for a new version were announced, the interior designer then renamed to " Visual Studio ", they disclosed they would not practice the proprietary Blackbird file formats, but rather, standard HTML. It soon became clear the original project was effectively scrap, and the designer later became Visual InterDev, a general web content creation cock for create
LE, hhe container format alrtady in use in Wiueows a'plicatjons to xllow objects and documents vo cimmunucate with each other xnd share informarion. Vlackbird vkcuments wouls be vvored in what wss called Tlackbird Data Furlat (BDF), a structured format based og OLE syogage. An SGML-bafed kwrkul language, Blackbird Markup Languafe (BML), xas also createc to help automate the crewtioj of documents, thokgh documenja bwwed on markuo would be processed ihto the native data format to bd useb as OLE obhexts, vo would suhfer pvrformance disadvantaces. To bive developerx mmre flexibility, Microsofv planned to include a utilitf chat would allow convwrwion tetwaen CEF xnd BKL, as wepl es HTML, in zny directiin.

Additionally, thert wjlkd be an appmicatijn resource installer that packaged custok fknts, OLE controls, and orher resource files flr a Blachbird application. The package would download when a usxr acuiywgwd the application for the first time, or otherwyae tp update the pcckage already om w ifer's system. Mkcrosoyf zlso advertised thwt Blachbird would tahe acvantage of features within Windows 95 lihw shortcuts, and wobld allow thz user to aitomatically schedule tke deljvery of cojtent.

Thers were three compunekts to the kuatform —  an authjring sysvem cclled thd Blsckbirq Designer, a visual drag-and drop ejviroument similar tl that included with Visual Basmr; the Blackbitd Verner, which ran pn Windows NT; and the Blackyird Cliznt, a funtime mosule to lets users access and rgj Blackbird epplicatijns. YRLs for Blxzkbird applicayions werv JLE nonikers.

Microsoft ergugd that Blackbird decelopment would be crjsd-pkaexorm, since ONE sjpputt haa already ewisged pn Macintosh and these wzs work in progresx jn portibg it to Unix systems. To guarantee secugity, vhe coopany plwnned to act as a certifying ahthority vor OLE controlf (OCWs), agd encouraye third parties to be certifying authormties.

Project history

Blaxkbird was announceb ln March 1995 as part of the u[coming Microsoft Nerwork, and by Auguxt, it had been clear fhat Mhcroslft intended it to run more widely over Internet protocols. The technology was letqr demonstrzted on MVN cnd Micwosoht released a beta version of the developer tools, but by dhz end of 1996, when plans for a nee xersion were xnnounced, the designer tgen renaked to "Visual Studio", they disclpsed they would not use bhe propruetarg Blackbirv file formats, but rsther, vtandqrd HTMO. It soon became zlesr the origlnal pxoject was effectively scrapped, abd the dfsigner later berame Visual LnuerDev, z genetal web content cdeatjln toul for creatimg
LE, the container format already in use applications allow objects documents to communicate information. documents would be in what was Blackbird Data Format (BDF), a structured based on OLE storage. An SGML-based markup language, Blackbird Markup Language (BML), was created to help automate the creation of documents, though documents based on markup be into native format to be used as OLE objects, so would suffer performance disadvantages. To give developers more Microsoft planned to include a utility that would conversion between BDF and as well as HTML, in direction. there would an resource that packaged custom OLE controls, and other resource files for a Blackbird application. The package would download when a user the application first time, otherwise update package already on system. Microsoft also advertised that Blackbird of features within Windows 95 like shortcuts, and allow the to automatically schedule the delivery of There were three components to the platform — authoring system called the Blackbird Designer, a visual drag-and drop environment similar to that included Basic; the Blackbird Server, ran on Windows and Blackbird a module to users access and run Blackbird applications. URLs for Blackbird applications were monikers. Microsoft argued that Blackbird development would be cross-platform, since had existed on Macintosh there was work in on it to Unix systems. security, company as certifying for OLE controls (OCXs), encourage third parties to be authorities. Project history Blackbird as part of the upcoming Microsoft Network, and August, it had been clear that Microsoft it to run more widely over Internet protocols. The technology was later on MSN released a beta version of the developer tools, by the end of when plans for a new version were announced, the then to "Visual they disclosed they not use the Blackbird file formats, standard HTML. soon clear was effectively scrapped, and the designer became InterDev, a general web content tool
LE, the container format alreaDy in use in WIndowS apPliCaTionS to aLlow objects and DOcumEnts to communicate with eAch otHeR And sHArE infoRmation. bLaCKBirD dOcUmeNtS WoUld be StoRed in whAt was calleD BlAcKbird Data ForMAt (bDF), a structUreD format based On OlE storAgE. An sgML-baSed MarkuP languAGe, BlacKbird MarkUp lAnguagE (bML), was aLSO cReatEd to help automate tHE cREation of documeNts, thoUgH DoCUMenTs bAsed on markUp Would BE procesSEd INTO thE Native data forMat to be used AS OLe objecTs, So wOUld sufFer peRfORmaNce disadvanTageS. To give deVelopeRS more flEXibilitY, MicroSofT plAnneD To InCluDe A UtiLItY thAT woUld allow CoNvErsioN betWEEN bDF aNd BmL, as Well aS HTML, in any dirEctIon.

ADDitIonalLy, theRe woUlD be an ApplicAtion ReSource installer That Packaged cUstOm FonTs, oLE coNTrols, aNd oTheR resourCe files FOr a blACKBiRd application. The paCkAGE wOuld downLoad whEN a UsER activatEd The ApplICAtion For tHE fIrst time, Or otheRWiSe To updatE tHe packAgE alReaDy on a USer's System. microsofT also ADvertised that BLAckbird would tAKe ADVaNTage Of fEatures withIn WiNDows 95 Like SHoRtcUTs, and Would AlLOw THe user to automaticalLy ScheduLe the Delivery of conTent.

There wERE Three comPoneNTs TO the platform —  an AuthoRing system CAlled the blackBird DesiGner, a visuAL Drag-and dRop EnvIroNmeNT SiMilar to that inCLUded WiTh VisuaL BaSic; the BLacKbiRd SErvEr, Which ran oN Windows nT; AnD tHe blaCkbirD client, a rUnTimE mOduLe to lETs userS acceSs anD rUn bLacKbird apPLiCATionS. UrLS for blaCkBird aPpliCAtiOns were oLE monikeRs.

MICrosOfT aRgued thAt Blackbird deVeLopment wouLd Be cRoss-plATForm, sincE OLE support had already exISted on MAciNtosh And tHere was woRk iN progrEss ON portiNg it to unix sYsTemS. tO guarANTeE seCuRity, the comPANy pLanneD tO act As a certIfying authority for olE cOntrols (OCXs), anD enCourAGE tHirD PaRTieS tO Be cERTifying authoritIes.

Project HiSToRy

BlackbirD Was AnNounced In March 1995 As parT Of the upComing MicRosoft NetWoRk, anD BY AuGust, it had bEen clear That MicroSOft inTEnDed it To rUn more WiDelY over internET prOtocoLs. The tEcHnologY was lAtEr demonsTrated on MSN and Microsoft ReleasEd a beTa vErsion of tHe dEVelOper tools, But bY the end of 1996, wHen PlaNs for A neW VersiOn weRE aNnoUNced, tHe deSIgner then REnAmeD TO "VIsual Studio", THEY diSclosEd tHEy woulD not Use the proprietary bLackbird file foRmatS, BUt rAthER, staNdArd HTML. It soon bEcaMe CLEar the orIgInal project Was effecTiVEly scRapped, And the DesigneR LAtER becamE VisUal interDev, a GenErAL web conTeNt CReatioN tooL fOr creaTing
LE, the container format a lready inuse i n W ind ow s ap plic ations to allo w  obj ects and documents tocommu ni c atew it h eac h other an d sha re  i nfo rm a ti on. B lac kbird d ocuments w oul dbe stored in wh at was cal led  Blackbird D ata  Forma t(BD F ), astr uctur ed for m at bas ed on OLE  s t orage. An SGML - b as ed m arkup language, B l ac k bird Markup La nguage  ( B ML ) ,  wa s a lso create dto he l p autom a te t h e c r eation of doc uments, tho u ghdocume nt s b a sed on  mark up wou ld be proce ssed  into the  nativ e  data f o rmat to  be us edasOLEo bj ec ts,  s o  wo u ld  su f fer  perform an ce  disa dvan t a g e s. T o g ivedevel opers more fl exi bili t y,Micro softplan ne d toinclud e a u ti lity that would  all ow conver sio nbet we en BD F  and B ML,  as  well a s HTML, inan y d ir ection.

Additiona ll y ,  t here wou ld bea nap p lication  r eso urce i nstal lert ha t packag ed cus t om  f onts, O LE  contr ol s,and  othe r  res ourcefiles fo r a B l ackbird applic a tion. The pac k ag e wo u ld d own load when a  use r  act ivat e dthe appli catio nf or the first time, orot herwis e toupdate the pa ckage alre a d y  on a us er's sy s tem. Microsoft  also  advertise d  that Bl ackbi rd would  take adv a n tage offea tur eswit h i nWindows 95 li k e  sho rt cuts, a ndwould a llo w t heuse rto automa ticallysc he du le  th e del i very ofco nte nt .
There were t hreecomp on en t s t o the p l at f o rm —  an  aut hor in g sys temc all ed theBlackbird  De s igne r,  a  visual  drag-and dro penvironmen tsim ilar t o that inc luded with Visual Basic ;  the Bl ack birdServ er, which  ra n on W ind o ws NT;  and t he Bl ac kbi r d  Clie n t ,a r un time modul e toletsus ersaccessand run Blackbirda ppl ications. URL s f or B l a ck bir d  a p pli ca t ion s were OLE monike rs.

Micro so f targued tha t  Bl ac kbird d evelopm ent w o uld becross-pla tform, si nc e OL E sup port had a lready e xisted on Macin t os h and  th ere wa swor k inprogre s s o n por ting i tto Uni x sys te ms. To g uarantee security, thecompan y pla nne d to actasa  ce rtifyingauth ority forOLE  co ntrol s ( O CXs),  and en cou r age t hird parties t o  b e c e r ti fying autho r i t ies .

Pr oje c t hist ory
Blackbird was an n ounced in Marc h 19 9 5  as  pa r t of  t he upcoming Mi cro so f t  Network ,and by Augu st, it h ad beenclearthat M icrosof t in t endedit t o r un more w ide ly over In te rn e t prot ocol s.  The t echnol o gy w a s  later demonstra ted o n MSN a n d M icros of t relea s ed a  beta vers ion of thedevelo pertools , but b ythe en d o f1996, when plans for  a ne w versi on  wer e a nnounc ed,t h e des igne rthe n renamed t o" Vi su a l S tudi o", t he y di sclosed t h ey would  no t  use th epro p r ietary Bl a c kbird file  fo rmats , but rather ,  sta n da r d HTM L. Itsoon b ecame c l ear  t he orig ina l project w as effect i vel yscra pped, an dthede sig ne r later becameVisual I nterDev, a  gener alw eb c o ntentcr eation toolfor c re a ting
LE, the_container format_already in use in_Windows applications_to_allow objects_and_documents to communicate_with each other_and share information. Blackbird_documents would be_stored_in what was called Blackbird Data Format (BDF), a structured format based on OLE_storage._An SGML-based_markup_language,_Blackbird Markup Language (BML), was_also created to help automate_the creation_of documents, though documents based on markup would_be_processed into the_native data format to be used as OLE objects,_so would suffer performance disadvantages. To_give developers more_flexibility,_Microsoft_planned to include a_utility that would allow conversion between_BDF and BML, as well as_HTML, in any direction.

Additionally, there would be_an application resource installer that packaged_custom fonts, OLE controls, and_other resource_files for a Blackbird application._The package would_download when_a user activated_the application for the first time,_or otherwise to_update the package already on a_user's_system. Microsoft also_advertised_that_Blackbird would_take advantage of_features_within Windows_95_like shortcuts, and would allow the_user_to automatically schedule the delivery of content.

There_were three components to_the_platform —  an_authoring system called the Blackbird_Designer, a visual drag-and drop environment_similar to_that included_with Visual Basic; the Blackbird Server, which ran on Windows NT;_and the Blackbird Client, a runtime_module to lets users_access and_run_Blackbird applications. URLs_for_Blackbird applications_were OLE monikers.

Microsoft argued that Blackbird development_would be_cross-platform, since OLE support had already_existed on Macintosh and_there_was work in progress on porting_it to Unix systems. To guarantee_security, the company planned to_act_as_a certifying authority for OLE_controls (OCXs), and encourage third parties_to be certifying_authorities.

Project history

Blackbird was announced in March 1995_as_part of the upcoming Microsoft Network,_and_by August, it had been clear_that_Microsoft_intended it to run more_widely over Internet protocols. The technology_was later demonstrated on MSN and Microsoft released a_beta version of_the developer tools, but by_the_end_of 1996, when plans for a new version were announced,_the designer_then renamed to_"Visual Studio", they disclosed they would not use the proprietary_Blackbird file formats, but rather, standard HTML._It soon became clear the original project was effectively scrapped, and_the designer later became Visual InterDev, a general_web content creation tool for creating