PDF Essential ASP.NET Web Forms Development: Full Stack Programming with C#, SQL, Ajax, and JavaScript 1st Edition Robert E. Beasley download
PDF Essential ASP.NET Web Forms Development: Full Stack Programming with C#, SQL, Ajax, and JavaScript 1st Edition Robert E. Beasley download
com
https://textbookfull.com/product/essential-asp-net-web-
forms-development-full-stack-programming-with-c-sql-ajax-
and-javascript-1st-edition-robert-e-beasley/
OR CLICK BUTTON
DOWNLOAD NOW
https://textbookfull.com/product/biota-grow-2c-gather-2c-cook-loucas/
textboxfull.com
Pro MERN Stack: Full Stack Web App Development with Mongo,
Express, React, and Node Vasan Subramanian
https://textbookfull.com/product/pro-mern-stack-full-stack-web-app-
development-with-mongo-express-react-and-node-vasan-subramanian/
textboxfull.com
https://textbookfull.com/product/mastering-full-stack-react-web-
development-1st-edition-tomasz-dyl/
textboxfull.com
Pro MERN Stack: Full Stack Web App Development with Mongo,
Express, React, and Node 1st Edition Vasan Subramanian
(Auth.)
https://textbookfull.com/product/pro-mern-stack-full-stack-web-app-
development-with-mongo-express-react-and-node-1st-edition-vasan-
subramanian-auth/
textboxfull.com
Pro MERN Stack: Full Stack Web App Development with Mongo,
Express, React, and Node 2nd Edition Vasan Subramanian
https://textbookfull.com/product/pro-mern-stack-full-stack-web-app-
development-with-mongo-express-react-and-node-2nd-edition-vasan-
subramanian/
textboxfull.com
https://textbookfull.com/product/web-development-with-node-and-
express-leveraging-the-javascript-stack-2nd-edition-ethan-brown/
textboxfull.com
Robert E. Beasley
Essential ASP.NET Web Forms Development: Full Stack Programming with C#, SQL,
Ajax, and JavaScript
Robert E. Beasley
Franklin, IN, USA
Acknowledgments�������������������������������������������������������������������������������������������������xvii
Preface�������������������������������������������������������������������������������������������������������������������xix
Part I: Overview���������������������������������������������������������������������������������������������� 1
Chapter 1: Web Application Development���������������������������������������������������������������� 3
1.1 Introduction����������������������������������������������������������������������������������������������������������������������������� 3
1.2 Client-Server Model���������������������������������������������������������������������������������������������������������������� 4
1.3 .NET Framework��������������������������������������������������������������������������������������������������������������������� 8
1.4 Object-Orientation Concepts��������������������������������������������������������������������������������������������������� 9
1.4.1 Classes and Objects����������������������������������������������������������������������������������������������������� 10
1.4.2 Properties��������������������������������������������������������������������������������������������������������������������� 12
1.4.3 Methods������������������������������������������������������������������������������������������������������������������������ 12
1.4.4 Events��������������������������������������������������������������������������������������������������������������������������� 13
1.4.5 Encapsulation��������������������������������������������������������������������������������������������������������������� 13
1.4.6 Inheritance������������������������������������������������������������������������������������������������������������������� 14
1.5 ASP.NET and C# Programming���������������������������������������������������������������������������������������������� 21
1.6 Visual Studio������������������������������������������������������������������������������������������������������������������������� 22
1.7 Starting a New Project���������������������������������������������������������������������������������������������������������� 23
1.8 Solution Explorer������������������������������������������������������������������������������������������������������������������� 24
v
Table of Contents
vi
Table of Contents
vii
Table of Contents
viii
Table of Contents
ix
Table of Contents
x
Table of Contents
xii
Table of Contents
Index��������������������������������������������������������������������������������������������������������������������� 559
xiii
About the Author
Robert E. Beasley is Professor of Computing at Franklin College in Franklin, Indiana,
USA, where he teaches a variety of software engineering courses. He received both his
BS and MS degrees from Illinois State University and his PhD from the University of
Illinois at Urbana-Champaign. He has been developing software since 1981, has been
an active software consultant in both the public and private sectors since 1987, and has
been teaching software engineering since 1995. He has authored three books on software
engineering, contributed chapters to two books, published over 50 articles in refereed
journals and conference proceedings, and delivered numerous speeches and keynote
addresses at international conferences.
xv
Acknowledgments
For any project like this to be successful, input is required from a number of people.
I would like to thank David G. Barnette for providing a significant amount of technical
feedback on the entire book, Elijah M. Beasley for providing a number of suggestions
for improving the flow and continuity of the book, and my other software engineering
students for reporting misspellings, typos, and other defects as they were encountered.
xvii
Preface
Audience
This book was written for anyone interested in learning the ASP.NET Web Forms,
C#.NET, SQL, Ajax, and JavaScript Web application development stack, including
novice software developers, professional software developers, and college or university
students enrolled in a one-semester course or two-semester sequence of courses in Web
application development.
Organization
This book helps you become a pro in one of the most effective and widely used
technology stacks for developing highly interactive, professional-grade, database-driven
Web applications—ASP.NET Web Forms, C#.NET, SQL, Ajax, and JavaScript. It takes
you from beginner to pro in no time. In Part 1, you become familiar with some of the
major concepts, methodologies, and technologies associated with .NET Web application
development. In this part, you learn about the client-server model, the .NET Framework,
the ASP.NET and C# programming languages, and the Visual Studio integrated
development environment. In Part 2, you learn how to develop a single-page .NET
Web application. In this part, you learn how to create a page and add server and data
validation controls to it. The concepts in this part of the book lay the foundation required
for learning the C# programming language in the context of an ASP.NET Web application.
In Part 3, you learn how to program in the C# programming language. In this part, you
learn how to perform assignment operations, conversion operations, control operations,
string operations, arithmetic operations, date and time operations, array operations,
collection operations, and file system operations, as well as create custom C# classes—in
the context of a .NET Web application. In Part 4, you learn how to develop a multiple-
page .NET Web application. In this part, you learn how to maintain state between pages
and create master pages, themes, and navigation controls. In Part 5, you learn how to
connect a .NET Web application to a SQL Server database. In this part, you learn to read
a database schema, program in the SQL programming language, utilize data binding,
xix
Preface
perform single- and multiple-row database table maintenance, and write code behind
database operations. And in Part 6, you learn how to enhance the interactivity of a .NET
Web application. In this part, you learn to generate email messages, make use of basic
Ajax controls and the Ajax Control Toolkit, and program in the JavaScript programming
language.
Features
Class Focus
A class diagram is included for every class discussed in the text. Each class diagram
articulates some of the most important properties, methods, and events of the class. For
those properties, methods, and events that are not included in the class diagram, a link
to the official class reference is provided.
Real-Life Examples
A significant proportion of the examples in the text are drawn from the real-life
experiences of the author’s own software development practice that began in 1987.
Accessible Language
Although the subject matter of this book is highly technical and specialized, trendy and/
or arcane language that is inaccessible to the average learner is either clearly defined or
replaced in favor of clear and generalizable terminology.
xx
PART I
Overview
CHAPTER 1
Web Application
Development
1.1 Introduction
The concept of hypermedia (i.e., the combination of hypertext and media) was first
envisioned in 1945 by American engineer, inventor, and science administrator Vannevar
Bush. However, it wasn’t until much later that the technology required to support such a
concept was mature enough to make hypermedia something most of us take for granted today.
In 1969, the Advanced Research Projects Agency Network (ARPANET) became the
first computer network to implement packet switching using the Transmission Control
Protocol/Internet Protocol (TCP/IP) suite—the protocol suite that forms the technical
foundation of the Internet today. Packet switching is a method of data transmission
that requires three basic steps to get data (e.g., remote computer screens, files, email
messages, Web pages) from one computer on a network to another. First, at its origin, the
data to be transmitted is separated into a sequenced set of relatively small parts called
packets. Second, the packets are transmitted independently from their origin to their
final destination over routes that have been determined to be optimal for each packet.
And third, after all the packets have made their way to their final destination, the data is
reassembled from its packets. Early TCP/IP Application Layer protocols included Telnet
for logging in to remote computers, File Transfer Protocol (FTP) for transmitting files
from one computer to another, and Simple Mail Transfer Protocol (SMTP) for sending
email messages. These protocols are still in heavy use today.
Although the Internet was alive, well, and growing from the late 1960s through the late
1980s, there was no World Wide Web (a.k.a., Web). However, this was about to change.
In 1989, development of the Hypertext Transfer Protocol (HTTP) was initiated by English
scientist Tim Berners-Lee at the European Organization for Nuclear Research (a.k.a., CERN)
in Meyrin, Switzerland—a suburb of Geneva. This protocol was to become the standard for
3
© Robert E. Beasley 2020
R. E. Beasley, Essential ASP.NET Web Forms Development, https://doi.org/10.1007/978-1-4842-5784-5_1
Chapter 1 Web Application Development
governing the communication between distributed hypermedia systems. With the definition
of the first official version of HTTP in 1991, the Web, the hypermedia part of the Internet, was
born, and HTTP became another TCP/IP Application Layer protocol like its predecessors
Telnet, FTP, and SMTP. Shortly thereafter, Berners-Lee created the very first Web browser.
This browser became available to other researchers in January 1991 and was released to the
public in August 1991.
Early on, the Web was simply a large collection of static Web pages. These pages
did little more than display formatted text and visual media (i.e., images, graphics,
animations, videos) and permit us to download files and play audio recordings. Today,
however, the Web is a massive collection of both static and dynamic Web pages. And
thanks to programming languages like ASP.NET, dynamic Web pages can do much more
than static Web pages can. In addition to the things static Web pages allow us to do,
dynamic Web pages allow us to interact with the items displayed on a Web page. They
also permit us to do things like edit the data on a page, check the data for errors, and save
the data to a database.
In this chapter, we will begin by looking at the client-server model, which is a
computing approach that distributes processing between servers and clients. Next, we
will introduce the .NET Framework. The .NET Framework is Microsoft’s Windows-based
software development and execution framework. Then, we will discuss ASP.NET and
C# programming. ASP.NET is a software development framework that includes all of
the classes necessary for building modern, sophisticated Web applications, and C# is
a general-purpose programming language for building a variety of application types,
including Web applications and Windows applications. After that, we will look at Visual
Studio, which is Microsoft’s flagship integrated development environment (IDE). This
development environment permits us to code and test in several different programming
languages via a consistent user interface. And finally, we will learn how to start a new
ASP.NET Web Application project.
4
Chapter 1 Web Application Development
5
Chapter 1 Web Application Development
Recall that Web pages are either static or dynamic. The content and appearance of
a static Web page doesn’t change each time it is requested. Instead, it always looks the
same no matter how many times it is requested or who requests it. It is easy to tell if a
Web page is static because it has a file extension of .htm or .html. As we will see in the
next figure, this type of Web page only requires the attention of a Web server.
Figure 1-2 shows the processing cycle of a static Web page. As can be seen, a Web
client (e.g., a laptop computer running Internet Explorer) requests a Web page from a
Web server (e.g., a tower computer running IIS) via an HTTP request. One important
part of this request is the name of the requested Web page (e.g., Display_Products.html).
Two other important parts of the request are the IP addresses (i.e., the unique Internet
addresses) of the server and client. These are necessary so that the HTTP request can
make its way to the Web server and so that the requested Web page can make its way
back to the requesting Web client. When the Web server receives the HTTP request, it
locates the desired Web page file on its hard drive, attaches the file’s Hypertext Markup
Language (HTML) code to an HTTP response, and then sends the response to the
requesting Web client. When the Web client receives the HTTP response, it uses the
attached HTML code to format and display the requested Web page for the end user. If
the requested Web page does not exist on the server, the infamous 404 (i.e., Page Not
Found) error is passed back to the Web client where it is displayed for the end user.
Unlike the content and appearance of a static Web page, a dynamic Web page can
(and usually does) change each time it is requested. In fact, depending on when it is
requested and by whom, it usually contains different information (e.g., different customer
information) and can look completely different (e.g., different fields, different images). It is
easy to tell if a Web page is dynamic because it has a file extension that is associated with
dynamic Web pages. Examples of such file extensions are .aspx (active server page), .php
(hypertext preprocessor), and .jsp (java server page). As we will see in the next figure, this
type of Web page is processed by both a Web server and an application server. When a Web
application requires database functionality, a database server is required as well.
6
Chapter 1 Web Application Development
Figure 1-3 shows the processing cycle of a dynamic Web page. As before, a Web client
requests a Web page from a Web server via an HTTP request. In this case, however, the
request contains the name of a dynamic Web page (e.g., Display_Products.aspx) and the
state of any Web page controls (e.g., a name entered into a text box, a check mark placed
into a checkbox, a date selected from a calendar). When the Web server receives the
HTTP request and sees that the Web page has a file extension of .aspx, it passes processing
control to the application server where the business logic (e.g., ASP.NET and C# code)
of the Web page is executed. If the business logic of the Web page requires the services
of a database server (i.e., reading, inserting, updating, or deleting data), the application
server passes processing control to the database server (along with any pertinent input
parameters) where the database call (usually a Structured Query Language [SQL] call)
of the Web page is executed. Once the database call is executed, the response from the
database server (e.g., the retrieved data and/or the status of the call) is passed back to the
application server where it is processed (e.g., the retrieved data is formatted and/or the
status of the call is handled). After this, the application server passes its work back to the
Web server, where it locates the desired Web page file on its hard drive, formats the Web
page’s HTML based on the results of the application server’s work, attaches the resulting
HTML code to an HTTP response, and then sends the response to the requesting Web
client. When the Web client receives the HTTP response, it uses the attached HTML code
to format and display the requested Web page for the end user. Again, if the requested Web
page does not exist on the server, the infamous 404 (i.e., Page Not Found) error is passed
back to the Web client where it is displayed for the end user.
Keep in mind that although servers and clients usually run on separate computing
devices, they can run on the same device. As an example of the latter, we often use a Web
server (e.g., IIS Express), an application server (e.g., .NET Framework), a database server
(e.g., SQL Server), and a Web client (e.g., Internet Explorer) all installed on the same
machine when developing ASP.NET Web applications.
7
Chapter 1 Web Application Development
8
Chapter 1 Web Application Development
9
Chapter 1 Web Application Development
1
A non-static class can also contain static properties, static methods, and static events that we can
utilize immediately, without having to instantiate an object from the class.
10
Chapter 1 Web Application Development
Class
Namespace
Properties
Methods
Events
Reference
There is one more very important thing to remember about the class diagrams used
in this book. The event handler methods used to handle the events of a class will be
omitted to conserve space. Event handler methods are those methods that begin with
the word “On” and end with an event name. For example, OnInit is an event handler
method that is raised by the Init event. If the Init event is already displayed in the Events
section of the class diagram, then the OnInit event handler method will be omitted from
the Methods section of the class diagram to conserve space.
An object is a single instance of a class. For example, say we have an Employee class that
serves as the “template” for all employees. In this case, we might have an Employee object
that represents Jim J. Jones who has an email address of [email protected] and a password of
abc123. We might also have an Employee object that represents Mary M. Morris who has an
email address of [email protected] and a password of xyz789. These two distinct objects,
both of which are viewed as independent items, were instantiated from the Employee
class by constructing each one and then setting their respective Name, EmailAddress, and
Password properties. The ability to instantiate multiple objects from a single class is why, for
example, we can have several text box and button objects on a single Web page, and each one
of them can look and behave similarly yet differently.
11
Chapter 1 Web Application Development
1.4.2 Properties
Properties represent the data of a class. Properties are read from (via a get method) and
written to (via a set method). For example, the .NET TextBox class has a Text property.
If we wish to retrieve the value entered into a text box object, we would need to get this
property. As another example, the .NET Button class has a BackgroundColor property,
a ForegroundColor property, and a Text property. If we wish to display a gray button
with red lettering that says “Submit,” we would need to set these three properties
appropriately. Properties can be non-static or static.
1.4.3 Methods
Methods perform a function (i.e., a task that returns a value) or a procedure (i.e., a task that
does not return a value) and are invoked or called. There are two types of methods—non-static
methods and static methods.
A non-static method is a method that can be invoked, but only after an object
has been instantiated from its associated non-static class. For example, if we have an
Employee object that has been created from a non-static Employee class, and this class
includes a non-static ModifyPassword method, then we can invoke the Employee object’s
ModifyPassword method to update the employee’s password, something like this
booSuccess = Employee.ModifyPassword("abc123");
bytResult = Math.Sqrt(100);
where Math is a static class and Sqrt is a static method of the Math class.
12
Chapter 1 Web Application Development
1.4.4 Events
Events are things that happen. Events are raised by an end-user action or by something
else that occurs in time. When an event is raised, and we wish to handle that event, we
invoke a corresponding method. For example, the .NET Page class raises a Load event
every time a Web page loads. If we want to display something for the end user every time
the page loads, we would need to handle that event by adding the necessary code to the
corresponding OnLoad method. Keep in mind that we need not handle every event that
is raised. Events can be non-static or static.
1.4.5 Encapsulation
Encapsulation has two meanings in the context of object orientation. First, it refers to
the notion that a class’s properties (i.e., data) and methods (i.e., the processing that
operates on that data) are bundled together and treated as a single unit. Second, it refers
to the notion that a class’s properties and methods cannot be directly accessed by code
that resides outside of the class itself. Thus, in order to get or set a class’s properties
or execute a class’s methods, a class that requires such operations must request them
from the class that contains the desired properties or methods. This idea is referred
to as information hiding. Although the concept of information hiding is an important
guideline of object orientation, the .NET programming languages permit us to explicitly
relax or enforce such access restrictions by declaring properties and methods as private
(i.e., they can only be accessed by code within the same class), protected (i.e., they can
be accessed by code within the same class and by any related subclasses), or public (i.e.,
they can be accessed by code in any other class).
One of the benefits of encapsulation is that it shields the internals of a class from
other classes so that they can utilize the class’s functionality without concern for how the
class actually performs its duties. The only thing the other classes need to know about
the class is what inputs it requires and what outputs it produces—that is, knowledge of
the class’s interface. In addition, encapsulation facilitates code refactoring (e.g., making a
method more efficient or easier to maintain). This is because we can modify the methods
of a class without disrupting the class’s use by other classes—as long as the modifications
do not affect the class’s interface. Another benefit of encapsulation is that it encourages
us to think through all of a class’s properties and methods and to keep them together in
one place. This makes coding, testing, and maintenance much easier.
13
Another Random Scribd Document
with Unrelated Content
pris et toute la poissance de l’Escoce ruée jus, dont il avoit eu
esperance que par la guerre que les Escos euissent fait en
Engleterre, li rois englois se fust levé dou siège de devant Calais, or
estoit tout dou contraire, et bien trouvoit qui li disoit: «Chiers sires, il
vous fault ces bonnes gens conforter, car se vous perdés la forte ville
de Calais, ce vous sera mis trop grans prejudisses et à vostre
roiaulme, et aueront les Englois trop biel à venir et à ariver à Calais
et courir en France et là retraire et retourner en lor pais.» Li rois, qui
fu uns moult vaillans homs et moult usés d’armes, car de sa jonèce il
les avoit acoustumées et continuées, consideroit bien toutes ces
coses, et sentoit aussi que on li disoit verité; si en respondoit ensi et
disoit: «Par m’ame et par mon corps, vous avés cause de tout ce
dire, et no uy pourverons; car il nous tourneroit voirement à trop
grant blame et damage, se nous perdions Calais.»
Et avint que, sus l’espoir de reconforter ceuls de Calais et lever le
siège, li rois de France fist un très grant mandement de chief en qor
son roiaulme, et dist que il ne voloit fors guerriier des gentils
hommes dou roiaume de France, et que des conmunautés amener
en bataille, ce n’est que toute perte et empecemens, et que tels
manières de genz ne font que fondre en bataille, ensi conme la nive
font au solel; et bien avoit aparu à la bataille de Crechi, à la Blanqe
Taqe, à Kem en Normendie et en tous les lieus où on les avoit
menés, et que plus il n’en voloit nuls avoir, fors les arbalestriers des
chités et des bonnes villes. Bien voloit lor or et lor argent pour paiier
les coustages et saudées des gentils honmes, et non plus avant; il
demorassent as hostels et gardaissent lors fenmes et lors enfans, il
devoit souffire, et fesissent leur labeur et marceandise, et les nobles
useroient dou mestier d’armes, dont il estoient estruit et introduit.
Li rois de France, en istance que pour conforter la ville de Calais et
ceuls qui dedens estoient, aproça les marces de Piqardie et s’en vint
en la chité de Amiens. Et fu là le jour de la Pentecouste et toutes les
festes, et estendi ses mandemens et conmandemens parmi tout son
roiaulme, et mandoit et conmandoit très estroitement que tout
venissent sans nul delai, ses lettres veues, en la chité d’Amiens ou là
environ. Pour ces jours estoit connestables de France et usoit de
l’office messires Jaquemes de Bourbon, conte de Pontieu; et estoient
mareschal li sires de Biaugeu, qui se nonma Edouwars, et li sires de
Montmorensi, et mestres des arbalestriers, li sires de Saint Venant.
Et n’estoit mais nulle nouvelle en France de messire Godemar dou
Fai, mais estoit retrais en Normendie, sa nation, et là se tenoit sus le
sien, ne point il n’estoit en la grace dou roi.
Au mandement dou roi de France obeirent tout chil qui furent
escript et mandé, et vinrent li signeur en grant arroi, premierement li
dus de Bourgongne, li dus de Bourbon, li contes de Savoie, mesires
Lois de Savoie, son frère, messires Jehans de Hainnau, li contes de
Namur, li comte de Forois, le daufin d’Auvergne, le conte de
Boulongne, le conte de Nerbonne, le conte de Pieregorth, le conte
de Valentinois, le conte de Saint Pol, et tant de hauls barons et
signeurs que mervelles seroit à penser et detriance au nonmer. Et ne
sambloit point, quoi que la bataille de Creci euist esté en celle
année, que li roiaulmes de France ne fust ausi raemplis, apriès que
devant, de noble et poissans chevalerie, et estoient, qant il furent
tout asamblé et nombré, douse mille hiaumes.
Considerés la grant noblèce de gentils hommes, car casquns
hiaumes doit dou mains avoir cinq hommes dalés li; et estoient vingt
quatre mille arbalestriers geneuois, espagnols et hommes des chités
et bonnes villes dou roiaulme de France, tout en compte. Qant il
furent venu sus le Mont de Sangate, à deus lieues priès de Calais, il
se trouvèrent plus de cent mille hommes. Si ne furent pas sitos
venus ne asamblés, car il vinrent gens de Gascongne, tels que le
conte d’Ermignac, le conte de Fois, le conte de Berne, le conte de
Quarmain. Et tous les signeurs manda et pria li rois de France,
desquels il pensa à estre aidiés, car ce estoit se intension que il
leveroit le siège et combateroit les Englois, et pourtant faisoit il si
grandes pourveances.
Et envoia li rois de France des prelas de France et des chevaliers
pour tretiier as Flamens que il vosissent venir dalés leur signeur le
conte et faire à lui ce que il devoient, car voirement estoit li jones
contes de Flandres en celle assamblée dou roi. Li Flamenc li
remandèrent par ses gens meismes que il n’avoient point de signeur,
puisque il se absentoit de euls et ne les voloit croire, ne que pour li il
ne feroient riens, ne des rentes et revenues de Flandres il n’en
porterait nulles; et se avoir les voloit, il les venist bellement et
courtoisement despendre ou pais, et ouvrer par lor consel, mais il
n’avoit pas encores bien conmenchiet; et se il voloit perseverer en
ces opinions, il trouverait les Flamens plus durs et plus hausters que
onques n’euist fait son père.
Qant li rois de France entendi ces paroles et les responses des
Flamens, si les laissa ester, et considera assés lor manière et vei bien
que ils n’en aueroit aultre cose, et que point n’enteroit en euls sus
cel estat pour ratraire à sa volenté, fors par le moiien dou duch de
Braibant; mais pour le present, ils et ses consauls estoient cargiet de
si grant cose que à ceste des Flamens il ne pooit entendre. Si mist li
rois de France ceste cose en souffrance tant que à une aultre fois, et
entendi à voloir lever le siège de Calais.
Li rois d’Engleterre, qui se tenoit devant Calais à siège et estoit
tenus tout le temps, ensi que vous savés, et à grans coustages,
estudioit nuit et jour conment il peuist chiaus de Calais le plus
constraindre et grever; car bien avoit oy dire que ses adversaires, li
rois Phelippe de France, faisoit un très grant amas de gens d’armes,
et que il le voloit venir combatre; et si sentoit la ville de Calais si
forte que, pour asaut ne escarmuce que ils et ses gens y fesissent,
ils ne le poroient conquerre, et ces pensées et imaginations le
metoient sovent en abusions. Avoecques ce, sus son reconfort, il
sentoit la ville de Calais mal pourveue de tous vivres, car là dedens il
en i avoit ensi que riens.
Et encores, pour euls clore et tolir le pas de la mer, il fist faire et
carpenter un chastiel hault et grant de lons mairiens et de gros,
lesquels on aloit coper en la forest de Boulongne, et à force de gens
les dis mairiens on amenoit et à force de cevaus à Wisan ou là priès,
et estoient là bouté dedens la mer et aconvoiiet jusques sus le
sabelon devant Calais. Et là fu fais et carpentés li dis chastiaus, et fu
si fors et si bien bretesqiés que on ne le pooit grever. Et qant li
chastiaus fu tous ouvrés, li rois et ses consauls le fissent asseoir et
lever droit sus l’entrée dou havene, en l’enbouqure de la mer, et fu
pourveus d’espringalles, de bonbardes, d’ars à tour et d’aultres
instrumens bons et soubtieus. Et furent ordonné, pour garder le
havene et le chastiel, à la fin que nuls n’entrast ou dit havene oultre
lor volenté, soissante honmes d’armes et deux cens archiers. Ce fu li
ordenance qui plus constraindi ceuls de Calais, et qui plus tos les fist
afamer.
En ce temps enorta li rois d’Engleterre les Flamens, lesquels li rois
de France voloit mettre en tretié deviers li et le jone conte, leur
signeur, ensi que chi dessus est contenu, que il vosissent issir hors et
faire guerre avoecques lui. Et issirent des bonnes villes de Flandres
et dou tieroit dou Franch bien cent mille Flamens, et vinrent mettre
le siège devant la ville d’Aire, et ardirent et destruisirent tout le pais
de là environ, Saint Venant, Meureville, le Gorge, Estelles et le
Ventie, le Bassée et tout le pais que on dist l’Aleue. De quoi li rois de
France, qui faisoit son amas de gens d’armes, en envoia grant
fuisson en garnison à Saint Omer, à Lille et Bietune et par tous les
chastiaus, sus les frontières d’Artois et Boulenois, car on ne sçavoit
que les Flamens avoient en pensé. Mais li Flamench se retrairent
petit à petit, qant il orent fait lor escaufée, et retournèrent tous en
lors lieus. Fos 139 et 140.
P. 44, l. 22: desgarnis.—Ms. B 6: Là estoit le duc de Bourgongne,
le duc de Bourbon, le conte de Poitiers, le conte de Fois, le duc de
Normendie, aisné filz du roy, le conte d’Ermignach, le conte de
Savoie, messire Lois de Savoie ses frères, messire Jehan de Haynau,
le conte de Namur, le conte de Forès, le conte daufin d’Auverne, le
conte de Vendomme. Fos 386 et 387.
P. 45, l. 25: busioit.—Ms. A 7: musoit. Fº 156.
P. 46, l. 3: soixante.—Mss. A 8 à 10, 15 à 17: quarante. Fº 146.
P. 46, l. 12: Flandres.—Ms. B 6: environ le Saint Jehan Baptiste
l’an mil trois cens quarante sept. Et vinrent devant Ayre et y mirent
le siège. Sy y couvint le roy de Franche envoier gens d’armes. Sy
envoya de Saint Omer le duc de Bourbon, le conte daulpfin
d’Auvergne et messire Charles d’Espaigne, et dedens Aire le conte de
Danmartin, le conte de Poursien, messire Gui de Nielle, le sire de
Raineval et messire Joffroy de Digon; et ensy en toutes les fortresses
d’Artois mist bonnes gens d’armes pour les garder et deffendre
contre les dis Flamens qui furent pluiseurs fois bien reboutés. Et
exillèrent adonc les Franchois ung parc sur yeaulx que on clamoit la
Boe. Et s’en vint le roy de France demorer à la bonne chité d’Aras,
pour mieulx entendre à deffendre le conté d’Artois. Fos 388 et 389.
P. 46, l. 14 et 15: le Gorge.—Ms. A 7: la Gorge. Fº 156.—Mss. A 20
à 22: la Gorgue. Fº 234.
P. 46, l. 15: Estelles.—Mss. A 15 à 17: Estoilles.—Mss. A 20 à 22:
Esterres. Fº 234.
P. 46, l. 15: le Ventie.—Mss. A 15 à 17: la Ventre. Fº 163 vº.—Mss.
A 23 à 33, B 3: le Ventre. Fº 181.
P. 46, l. 16: l’Aloe.—Mss. A 20 à 22: l’Aleue. Fº 234.—Ms. B 3:
l’Alues. Fº 146.—Ms. B 4: l’Aleues. Fº 137 vº.
P. 46, l. 17: Tieruane.—Ms. A 29: Quant le roy Philippe entendi ces
nouvelles, il en fu tout courroucé.
Our website is not just a platform for buying books, but a bridge
connecting readers to the timeless values of culture and wisdom. With
an elegant, user-friendly interface and an intelligent search system,
we are committed to providing a quick and convenient shopping
experience. Additionally, our special promotions and home delivery
services ensure that you save time and fully enjoy the joy of reading.
textbookfull.com