Pro SharePoint 2013 App Development 1st Edition Steve Wright (Auth.)

Download the full version and explore a variety of ebooks
or textbooks at https://ebookultra.com
Pro SharePoint 2013 App Development 1st Edition
Steve Wright (Auth.)
_____ Follow the link below to get your download now _____
https://ebookultra.com/download/pro-sharepoint-2013-app-
development-1st-edition-steve-wright-auth/
Access ebookultra.com now to download high-quality
ebooks or textbooks

Here are some recommended products for you. Click the link to
download, or explore more at ebookultra.com
Pro SharePoint 2013 Business Intelligence Solutions 1st
Edition Manpreet Singh
https://ebookultra.com/download/pro-sharepoint-2013-business-
intelligence-solutions-1st-edition-manpreet-singh/
Pro SharePoint 2010 Search 1st Edition Josh Noble
https://ebookultra.com/download/pro-sharepoint-2010-search-1st-
edition-josh-noble/
Going Pro with Cubase 6 1st Edition Steve (Steve Pacey)
Pacey
https://ebookultra.com/download/going-pro-with-cubase-6-1st-edition-
steve-steve-pacey-pacey/
Pro SharePoint disaster recovery and high availability 2nd
Edition Stephen Cummins
https://ebookultra.com/download/pro-sharepoint-disaster-recovery-and-
high-availability-2nd-edition-stephen-cummins/

Digital Compositing for Film and Video 2nd Edition Steve
Wright
https://ebookultra.com/download/digital-compositing-for-film-and-
video-2nd-edition-steve-wright/
Learn iOS 8 App Development Second Edition James Bucanek
(Auth.)
https://ebookultra.com/download/learn-ios-8-app-development-second-
edition-james-bucanek-auth/
ADO NET From Novice to Pro Visual Basic NET Edition Peter
Wright (Auth.)
https://ebookultra.com/download/ado-net-from-novice-to-pro-visual-
basic-net-edition-peter-wright-auth/
National Accounts of Oecd Countries Financial Accounts
2013 Edition 2013 Volume 2013 Oecd Organisation For
Economic Co-Operation And Development
https://ebookultra.com/download/national-accounts-of-oecd-countries-
financial-accounts-2013-edition-2013-volume-2013-oecd-organisation-
for-economic-co-operation-and-development/
Learn BlackBerry 10 App Development A Cascades Driven
Approach 1st Edition Anwar Ludin (Auth.)
https://ebookultra.com/download/learn-blackberry-10-app-development-a-
cascades-driven-approach-1st-edition-anwar-ludin-auth/

Pro SharePoint 2013 App Development 1st Edition Steve
Wright (Auth.) Digital Instant Download
Author(s): Steve Wright (auth.)
ISBN(s): 9781430258858, 1430258853
Edition: 1
File Details: PDF, 14.02 MB
Year: 2013
Language: english

For your convenience Apress has placed some of the front
matter material after the index. Please use the Bookmarks
and Contents at a Glance links to access them.

v
Contents at a Glance
About the Author��xv
About the Technical Reviewer��xvii
Acknowledgments��xix
Introduction��xxi
Chapter 1: Introduction to SharePoint Apps
■
■ ��1
Chapter 2: Creating and Debugging Apps
■
■
��31
Chapter 3: Managing the App Life Cycle
■
■ ��49
Chapter 4: Client-Side Logic with JavaScript
■
■ ��69
Chapter 5: Accessing the SharePoint Environment
■
■ ��113
Chapter 6: SharePoint App Security
■
■ ��145
Chapter 7: Web Services with REST and OData
■
■ ��185
Chapter 8: Business Connectivity Services
■
■ ��225
Chapter 9: App Logic Components
■
■ ��245
Chapter 10: Developing the User Experience
■
■ ��283
Chapter 11: Accessing SharePoint Search
■
■ ��313
Chapter 12: Using SharePoint’s Social Features
■
■
��331
Chapter 13: Enhancing Apps with SharePoint Services
■
■ ��351
Chapter 14: Using Other App Environments
■
■ ��371
Index��399

xxi
Introduction
SharePoint 2013 Server and SharePoint Online provide an entirely new model for developing enterprise solutions
called the Cloud App Model. This style of application is architected to run in a hosted environment without unduly
impacting the host servers. This provides for levels of scalability and reliability that were difficult, or impossible, to
achieve using SharePoint’s previous models that included full-trust and sandboxed solutions.
Pro SharePoint 2013 App Development contains the techniques for delivering advanced solutions on the
SharePoint 2013 platform. Using step-by-step tutorials, the reader creates and elaborates on a sample SharePoint app
throughout the course of the book. Once complete, the developer will be ready to tackle even the most demanding
SharePoint apps with confidence. In this book, we will cover the following points:
We will introduce the Cloud App Model architecture for creating and hosting SharePoint apps.
•
We will walk through the creation and deployment of a complete solution.
•
We will examine the security features of the SharePoint app model.
•
We will learn to leverage SharePoint data in our apps over the network, securely.
•
We will learn to utilize search and other SharePoint services to create rich SharePoint solutions.
•
We will explore how to use these techniques to deliver data on a multitude of web and mobile
•
platforms.
This book is intended for developers and IT professionals responsible for delivering solutions on the SharePoint 2013
platform. These solutions may run on-site, in the cloud, or in a hybrid deployment across many locations. We will
provide the background and step-by-step introduction needed to create massively scalable SharePoint applications
using standard tools such as Visual Studio, and web standards such as HTML and JQuery. Once created, SharePoint
apps can be deployed internally or sold through the Microsoft SharePoint Store across the Internet.
The objective is to empower organizations to create a new generation of web-based applications on the
SharePoint platform. SharePoint enables both on-site and cloud-based deployments of mission-critical business
applications, using all of the same tools and technologies, regardless of the environment. Using modern web
standards for user interfaces, data access, and most important, security, SharePoint apps can safely break down the
wall between internal data and external customers.
The book is designed to introduce each technique in the order necessary for each solution to build on the ones
that have come before. In some cases, it may be necessary to use a technique before we have discussed it fully.
In these cases, we will try to convey the necessary information and refer the reader to the later section.
Chapter 1: Introduction to SharePoint Apps
This chapter will introduce the new SharePoint app model. We will describe why the app model exists, how it differs
from the previous development models for SharePoint, and where SharePoint apps fit into the Microsoft ecosystem,
including Azure, Windows 8, and Windows Phone. This is the 30,000-foot view.

■ Introduction
xxii
Chapter 2: Creating and Debugging Apps
This chapter will introduce the tools used to create SharePoint apps. We will create a basic app that will begin
the book-wide sample project. This sample will be elaborated on in later chapters to demonstrate the techniques
presented in each chapter.
Chapter 3: Managing the App Life Cycle
This chapter will introduce the concept of an application life cycle. This includes all of the steps used to create and
maintain an app. We will look at each stage in the order they will be encountered by the typical app.
Chapter 4: Client-Side Logic with JavaScript
This chapter will provide the reader with an introduction to client-side programming using JavaScript and modern
programming patterns. We will introduce JavaScript, JQuery, and Knockout for those readers that are not familiar
with them. We will also introduce the Model-View-ViewModel (MVVM) design pattern that will be used throughout
the book.
Chapter 5: Accessing the SharePoint Environment
This chapter will cover the means of accessing data that is stored in SharePoint using the SharePoint 2013 client-side
object model (CSOM) libraries. This will include lists, libraries, and other SharePoint-specific content.
Chapter 6: SharePoint App Security
This chapter will cover the extensive security mechanisms that are inherent in deploying a mission-critical application
to SharePoint. This will include SharePoint apps’ means of performing both authentication and authorization. We will
also cover the security infrastructure used in Microsoft Azure.
Chapter 7: Web Services with REST and OData
This chapter will cover accessing data from network sources via generic data transfer methods. Unlike accessing
SharePoint with the CSOM, this style of data access uses the methods and data elements exposed through standard
interfaces such as REST and OData.
Chapter 8: Business Connectivity Services
In this chapter, we will examine the use of BCS within an app. These techniques allow an organization to leverage
internal data assets in the cloud, while retaining security and control of that data. We will discuss the best ways to
query and update BCS-based data.

■ Introduction
xxiii
Chapter 9: App Logic Components
Much of the development effort for an app involves accessing data and rendering a user experience. This chapter
will focus on the techniques for adding sophisticated logic within a SharePoint app. These techniques will allow us to
respond to SharePoint events and manage workflows.
Chapter 10: Developing the User Experience
This chapter will deal with the details of creating a modern user experience in a SharePoint app. We will cover the
different types of UIs that a SharePoint App can expose and the best tools to use for creating them. We will also learn
to make our apps conform to the style of the site in which they reside.
Chapter 11: Accessing SharePoint Search
The user interface in SharePoint 2013 sites can be driven more by search results than by content stored locally within
the SharePoint site. Microsoft calls this a “search-driven” site. In this chapter, we will discuss the techniques needed to
access and display search results with a SharePoint App.
Chapter 12: Using SharePoint’s Social Features
This chapter will describe the social features of the SharePoint 2013 platform as they relate to creating apps. We will
cover the MySite and SkyDrive Pro features, as well as newsfeeds, posts, and activities.
Chapter 13: Enhancing Apps with SharePoint Services
The SharePoint 2013 platform contains many integrated services that apps can leverage. These services provide
basic infrastructure such as logging and error reporting. They also provide specialized data for metadata, search,
and navigation. In this chapter, we will look at how to use some of these services to make our apps more robust and
functional.
Chapter 14: Using Other App Environments
This chapter will explore the Cloud App Model as it applies to platforms other than SharePoint and how apps can
be used to integrate information across the enterprise. SharePoint apps are only one type of “app” in the Microsoft
ecosystem. This chapter will delve into creating apps that cross between SharePoint, Windows 8 and RT, Microsoft
Office, and Windows Phone.
Summary
In creating the Cloud App Model, Microsoft has attempted to create an architecture that places cloud development
at the center. The focus was on creating rich Internet apps that are scalable, maintainable, and robust in a variety of
hosting environments. As a result, SharePoint apps can seem overly complex at times. As you will see in the coming
chapters, there are reasons for these design decisions. You are encouraged to absorb all of the concepts that you need
to design the next great app. Try not to get buried in the details the first time around.

1
Chapter 1
Introduction to SharePoint Apps
This chapter will introduce the new SharePoint 2013 application model. We will describe why the app model exists,
how it differs from the previous development models for SharePoint, and where SharePoint apps fit into the Microsoft
ecosystem, including Azure, Windows 8, and Windows Phone. In this chapter, we will go over the following points:
Why there is a new application model for SharePoint 2013.
•
How full-trust and sandbox solutions fit into the new paradigm.
•
How SharePoint apps relate to Microsoft’s online offerings, including Office 365,
•
Azure, and SQL Azure.
When and why to use SharePoint solutions in on-premise, cloud, and hybrid deployments.
•
The sample application that will be developed throughout this book.
•
Introduction to the Cloud App Model
In SharePoint 2013, Microsoft has introduced a new way to build solutions for SharePoint. This new method is called
the Cloud App Model. This model is similar to the development model introduced for Windows 8, the Windows
Runtime (WinRT), Office 2013, and Windows Phone 8.
A SharePoint app is a single package of functionality that can be deployed and activated on a site with very little
overhead or footprint on the SharePoint server farm. An app package contains all of the SharePoint artifacts (lists,
libraries, etc.) needed by the application along with any pages, scripts, styles, or other web files needed to complete
the application. Apps are designed to be easy to provision on a site and to be removed cleanly when no longer needed.
The Cloud App Model for SharePoint was designed with (surprise!) the cloud in mind. When an app is deployed
to a site, the configuration of the files and settings in SharePoint are handled automatically. The server farm is
protected from defective installation packages and file updates because apps cannot be installed like traditional
SharePoint solution packages. App package files are managed entirely by SharePoint itself.
When running in the cloud, it is imperative that no one application can produce an unmanageable load on the
farm or corrupt memory and require restarting of processes in the farm. SharePoint apps are prevented from causing
problems on the farm by eliminating use of the SharePoint Server-Side Object Model (SSOM) in app code. In fact,
all server-side code execution is off limits to SharePoint apps. To a developer familiar with developing applications
for previous versions of SharePoint, this would seem to make apps totally useless in a SharePoint context. As we will
see later, the combination of client-side technologies, like HTML and JavaScript, and sophisticated web service call
mechanisms, like REST and OData, make building scalable, reliable apps for SharePoint quite possible.
The rest of this chapter will introduce the concepts associated with the Cloud App Model as it applies to
SharePoint. We will discuss the components that make up a SharePoint app and how they are managed. The
remaining chapters of this book will discuss each of these in detail to enable you to create rich user applications in
SharePoint 2013.

Chapter 1 ■ Introduction to SharePoint Apps
2
Developing Solutions in Previous Versions of SharePoint
Let’s take a moment to revisit SharePoint 2010. Specifically, we will take a look at how custom applications were
developed and deployed prior to SharePoint 2013.
When designing a custom application for SharePoint pre-2013, we first had to decide what type of application
it would be: full-trust or sandboxed. We then had to consider things like what features that would go into the
application. The developer would create the files that make up the application and create feature manifests to manage
their installation. Finally, we would create a solution package file (.WSP) that could be deployed to SharePoint. Project
templates for Visual Studio made this process easier in later versions, but there were still times when the developer
had to work with raw XML or CAML files in order to accomplish even routine tasks.
For full-trust solutions, a farm administrator would need to deploy the solution package to each SharePoint server
in the farm. This would have the effect of copying files into various folders throughout the server farm. Most of these
files ended up in the “14 hive.” The hive is a folder on the server’s hard drive that contains many of SharePoint’s own
files, which might be overwritten or altered by some package installations. Finally, the farm administrator would need
to activate the features of the solution in order to begin using them within the farm.
Creating full-trust applications in SharePoint can have several unwanted side effects on the server farm’s stability
and performance.
All code in a full-trust application runs within SharePoint’s own server processes. Any
•
corruption caused by the application has the potential to crash the server or farm.
Any slow or inefficient code in an application can consume CPU cycles, memory, or disk space
•
on the farm’s servers and hurt performance.
If the application does not take appropriate security precautions, it can compromise
•
information stored in the farm because a full-trust application can always elevate its privileges
to perform virtually any action.
When deploying a solution file containing a full-trust application to a farm, extensive testing is required to ensure
that the application will not cause damage to the farm. As a result, many organizations have adopted policies that
drastically limit or completely rule out the use of full-trust applications.
In a hosted or cloud environment, the server farm may support multiple end-user organizations or tenants. In
these scenarios, including using SharePoint Online, full-trust applications are simply not an option. No outside code
can be allowed to run in full-trust without risking harm to other customers in the farm.
In SharePoint 2013, full-trust applications are still supported and are appropriate for certain types of applications.
Any custom functionality that deals with managing the farm or accessing specialized hardware may require elevated
privileges and should still be created as a full-trust application. These solution packages will continue to be supported
as they have been, but they are only for use in locally hosted, on-premise farm deployments. They are not appropriate
for any functionality being deployed to a hosted or cloud environment.
The other option, prior to the release of SharePoint 2013, was to create a sandboxed solution. These solutions are
developed using the same techniques and file formats as full-trust solutions, but with certain limitations.
Sandboxed applications do not run with full-trust and cannot elevate their privileges to
•
acquire it.
Sandboxed applications run in a separate isolated process to prevent them from corrupting
•
the server farm’s own processes.
Applications that run in the sandbox are only allowed to access a subset of the SharePoint
•
Server-Side Object Model (SSOM) through a proxy object that forwards the requests to the
main SharePoint processes.
Sandboxed applications are deployed and managed at the site collection level and can only
•
access resources within the local site collection. They cannot access other resources within the
farm or elsewhere on the network, even when using the Client-Side Object Model (CSOM).

3
The sandbox was introduced in SharePoint 2010 in an attempt to isolate custom applications from SharePoint
and limit their potential for harming the overall farm. While this was accomplished, the restrictions placed on
sandboxed applications have limited their usefulness. The sandbox model has also been found insufficient for hosting
and cloud deployments.
The code in a sandboxed application still runs on the servers in the SharePoint farm. Poorly
•
written or managed applications can still cause performance problems or limit scalability.
Sandboxed applications that corrupt their own memory or use too many resources may be
•
automatically restarted periodically, further draining server resources.
The limitations on what data can be accessed from a sandboxed application limits their
•
usefulness in enterprise-style applications that require broader access to SharePoint and
network resources.
Limiting access to the Server-Side Object Model, and the limited implementation of the
•
Client-Side Object Model in SharePoint 2010, made creating rich applications in the sandbox
very difficult or impossible.
Because sandboxed solutions are deployed at the site collection level, they are managed by
•
site collection administrators. These users have to install, activate, configure, and remove
these packages within each site collection they own. In many organizations, site collection
administration is delegated to non-technical power users who typically find managing solution
packages very confusing.
The sandbox was created to solve the application management problems created by full-trust applications, but
it has created new problems and imposes severe limitations on the types of applications that can be developed. As a
result, sandboxed solutions have been deprecated in SharePoint 2013. In this case, deprecated is Microsoft’s way of
saying “Oops, that didn’t work!” In practical terms, deprecated means that while the sandbox still exists in SharePoint
2013 for backward compatibility, it may not be a part of future releases. No new development should be done in
sandboxed solution packages.
With full-trust applications limited to living behind the organization’s firewall and sandboxed solutions on the
way out, how do we make the leap into the cloud? The answer, of course, is to create SharePoint apps using the Cloud
App Model.
Developing Apps for SharePoint 2013
Using apps for SharePoint is very similar to using apps on mobile devices such as Android- or iOS-based phones.
When a cell phone’s user wants to extend the functionality of their device, they go an app store of some sort. This
could be the Google Play Store for Android or the Apple Store for iOS. They find the app they want to install and select
it. The app is paid for, in some cases, and then automatically downloaded and installed on their device. Once the user
is finished using the app, they can uninstall it from their device as if it had never been there. The key to this usability is
the fact that no one but the end user ever needs to be involved.
In the case of SharePoint apps, an app is installed into a SharePoint site. As with mobile apps, a SharePoint app
can be acquired from the SharePoint Store (http://office.microsoft.com/en-us/store/apps-for-sharepoint-
FX102804987.aspx) managed by Microsoft, as shown in Figure 1-1. An app adds functionality to the site while it is
installed. The app may add SharePoint artifacts, such as lists and web parts, to the site. It can also add menu options,
pages, and other behaviors to the site.

4
The most important difference between a SharePoint app and a full-trust or sandboxed solution is in what is not
installed in SharePoint. A SharePoint app cannot contain any server-side code at all. The data access, business logic,
and user interface logic of the app is executed entirely outside of the SharePoint server farm. SharePoint may host the
HTML, CSS, and JavaScript files for the app, but the logic executes either within the client browser, or other user agent,
or on a remote web server outside of the farm. The end user is completely unaware of this, of course, but it makes all
the difference in the world to maintaining the scalability and stability of the farm.
In the Cloud App Model, SharePoint is essentially acting as a portal for storing data and exposing applications,
rather than directly hosting their logic. When creating a SharePoint app, the most important decisions to be made
involve distributing the components of the application in the most effective manner available. In the next section, we
will examine the concepts surrounding SharePoint app development and how these decisions are made.
Designing Cloud App Solutions
A typical application built using the Cloud App Model is composed of various components that communicate over
a network. This is contrary to traditional development models that assume that most of the code will run on one
platform (a server) or two platforms (a client and a server). In a cloud app, the assumption is that there is a client-side
user agent, either a web browser or mobile device, and one or more servers.
In the context of a SharePoint app, one of the servers will always be a SharePoint server. This server will manage
the user’s access to the app and host any SharePoint data that is included in the solution. It will not execute server-
side code. To perform custom logic, it will either hand off requests to other non-SharePoint web servers or it will serve
client-side code files to be executed by the client browser.
When constructing a SharePoint app, there are two basic patterns. One pattern emphasizes the use of client-side
code and the other uses server-side code executing outside of SharePoint.
Figure 1-1. The SharePoint Store

5
Client-Side Code Pattern
The simplest pattern for experienced SharePoint developers to understand is the client-side pattern. In SharePoint 2010,
Microsoft introduced the SharePoint Client-Side Object Model (CSOM). CSOM is a set of components that allow
applications running outside of SharePoint to connect to a SharePoint site using web services. These applications
become clients to the SharePoint site. These libraries have been greatly expanded in SharePoint 2013 and serve as the
basis for much of the client-side functionality available to SharePoint apps.
Apps built using a client-side approach are not that different from traditional web applications in which all of the
server-side logic has been refactored to the client side, as shown in Figure 1-2.
Figure 1-2. The client-side code pattern
The process begins when the user (1) requests a page from SharePoint that contains elements provided by an
app. There are different types of elements possible in a SharePoint app, from individual menu entries up to entire web
pages. In this example, the page contains an IFrame element whose content is supplied by the app. When the IFrame
is rendered in the browser, another request (2) is made to return the contents of the frame. The SharePoint app returns
all of the HTML, CSS, and JavaScript files needed to render the app’s user interface. Note that this does not include
rendering ASPX pages containing server-side code, since these are not permitted in an app. ASPX pages can be used
in this context, but they can only contain server controls, not code blocks or code-behind files.
In most cases, the contents to be displayed will not be static, but will require additional data to be returned. To
do this, the scripts rendered as part of the app will make client-side calls (3) to the SharePoint site to retrieve the data
to be displayed. Using web service calls and other techniques that will be described later, client-side calls can also be
used to access resources outside of SharePoint.
This pattern has the benefit of simplicity. All of the files needed by the app are stored in SharePoint and served
without the use of server-side code. In some cases, however, it may be necessary to execute parts of the app’s logic on
a server. This will require using the server-side pattern.

6
Server-Side Code Pattern
The client-side pattern eliminated server-side code by moving all logic to the client browser. What if doing so is not
possible, practical, or desirable? This is where the server-side pattern comes in, as shown in Figure 1-3.
Figure 1-3. The server-side code pattern
Using this pattern, instead of moving the logic to the client web browser, we are moving it to another web site
running outside of SharePoint. The remote web site can use server-side logic to render the HTML that is sent into the
app’s container. It can access data local to its host system or even access data within the app’s SharePoint site using
one of the client API libraries described later in this chapter.
This remote web site could be an ASP.NET site running under IIS, or a PHP site running under Apache. It could
be running within your organization, in the Windows Azure cloud, or in some other vendor’s cloud. Because the app’s
logic has been decoupled from the SharePoint server, it can run anywhere on the network.
In complex enterprise-level apps, you will find that neither the client-side model nor server-side model is
appropriate for all of the interactions needed by the app. These apps will most likely depend on a combination of
client-side and server-side techniques.
Deployment Options
To understand the deployment of apps to SharePoint 2013, it is important to start with the concept of a tenant.
A tenant refers to a customer or organization which uses a SharePoint farm but may share that farm with other tenants.
Starting in SharePoint 2010, SharePoint Server has supported a multi-tenant hosting model. This model is greatly
improved in SharePoint 2013.
Assume for a moment that you work for a web-hosting company that is going to sell space on a SharePoint server
farm to your customers. Your customers will be able to log on and use their SharePoint sites just as they would in an
intranet scenario. The difference is that they will be doing this over the Internet and there will be other customers doing
the same in different site collections on the same server farm. How would such an environment need to behave?

7
Each tenant’s data will need to be isolated from all others to ensure that it is only used for
•
that tenant.
You will need to track the usage of storage, network, and server resources so that you can bill
•
your customers appropriately.
You will need the ability to configure services, such as Search and Excel Services, relevant to
•
each tenant without affecting the others.
Any customizations (master pages, themes, etc.) deployed by one tenant should not affect any
•
other tenant’s sites.
Each tenant will need to be able to assign their own URLs to their sites without regard for the
•
structure of the SharePoint farm.
This type of environment is precisely what the multi-tenancy support in SharePoint Server is designed to allow.
Once this infrastructure is in place, there are several ways it might be used.
A commercial web-hosting company, as described above, could use multi-tenancy to host a
•
large number of smaller customers on one or more farms.
A large organization could use multi-tenancy to share a large centrally managed SharePoint
•
farm to host separate intranets for the various divisions or subsidiaries of the company. With
data isolation and usage analysis, a chargeback system could be used to bill the cost of the
farm back to the business units that use it.
A very large company, like Microsoft, could use these features to create a vast hosting
•
infrastructure for SharePoint sites.
Of course, the last of these options isn’t just a possibility—it’s called SharePoint Online and is now part of
Office 365.
When designing an app for SharePoint, it is useful to consider a multi-tenant environment even if the app isn’t
intended to be deployed in one. The reason is that this is the environment that the Cloud App Model was designed to
support. In fact, one of the most compelling scenarios for SharePoint apps is when they are used to support multiple
customers in multiple types of deployments. There are three main types of deployments: on-site (a.k.a. on-premise),
cloud, and hybrid.
An on-site deployment is the way SharePoint has been traditionally rolled out. The product is installed on a set of
servers behind an organization’s firewalls to support only that organization’s needs. This type of deployment has the
advantages of being internally controlled, having access to all of the organization’s network resources and support
for full-trust custom applications. On-site deployments also avoid the need to expose internal data resources to the
Internet, either by drilling holes in the firewall or moving the data into the cloud. The disadvantage is that all of the
cost of deploying and maintaining the farm’s infrastructure must be absorbed by the organization.
A cloud deployment shifts the burden of deploying and maintaining the infrastructure to a third party, such as
Microsoft in the case of SharePoint Online. This frees up resources for developing the content and functionality of the
site rather than maintaining the underlying servers. The disadvantage is a loss of control and a dependence on the
hosting organization to keep the farm robust. Cloud deployments can also include non-SharePoint platforms such as
Exchange Online, Windows Azure sites, and SQL Azure databases.
Right now, most organizations that use SharePoint do so in an on-site deployment. Over time, the cost savings of
cloud deployments will likely entice many organizations to move at least some of their deployments into the cloud.
This is where hybrid deployments come in (see Figure 1-4).

8
In a hybrid scenario, a SharePoint solution contains elements hosted on-site and in the cloud. In Chapter 6,
we will look at the security mechanisms that allow such an environment to function smoothly. There may be some
advanced or customized features of SharePoint, such as Business Intelligence or workflows, which organizations
chose to keep on-site for security, performance, or cost-of-ownership reasons. Hybrid deployments have the
advantage of maintaining control over the most vital and private parts of the solution, while offloading the
maintenance of as much infrastructure as is feasible.
SharePoint apps also support deployment scenarios beyond the Windows platform. Because all of the
components of a SharePoint app use standard web technologies to communicate and transfer control
(HTML, JavaScript, URLs, web service calls, etc.), there is no reason that these components have to be limited to the
Microsoft development stack or even to Windows-based servers.
An app’s non-SharePoint web content can be hosted on any type of web stack including one of
•
the LAMP variants—Linux, Apache, MySQL, and PHP, for example.
Non-Microsoft databases such as Oracle, DB2, and MySQL, and even non-relational
•
databases, can be used to serve data for a SharePoint app.
Media files can be served, streamed, queued, and delivered over Content Delivery
•
Networks (CDNs).
Web services hosted anywhere on the network, including behind firewalls, can be leveraged
•
as well.
Of course, creating these alternate types of web resources may require tools other than those supplied by
Microsoft. In this book, we will focus on the Microsoft toolset.
Distributing SharePoint Apps
After your app has been built and tested, it needs to be distributed. SharePoint and Office apps use the same type of
distribution system as apps for Android or iOS devices. In this case, Microsoft has established the Office Store
(http://office.microsoft.com/en-us/store/) for both Office and SharePoint apps.
The Office Store will sometimes be referred to as the SharePoint Store (http://office.microsoft.com/en-us/
store/apps-for-sharepoint-FX102804987.aspx) when referring only to apps for SharePoint. Developers and
organizations can publish apps to the Office Store and get paid for them. The store can also be used to distribute free
apps. Online service providers, such as LinkedIn or Facebook, will often provide free apps in online app stores like the
Office Store to provide easy integration with their services.
Figure 1-4. A hybrid SharePoint deployment

9
Not all apps belong in the SharePoint Store, however. What if your organization creates a line-of-business app
that is proprietary to your business? Obviously, you wouldn’t publish an app like that to a public app store. For these
cases, SharePoint 2013 contains a new site collection template called the App Catalog. The App Catalog acts as a
private app store that users of your sites can use to deploy custom apps from within your organization.
In a multi-tenant scenario, each tenant can have their own App Catalog.
Note
■
■ Chapters 2 and 3 will describe the app publishing and distribution process in more detail.
Development Environment
In order to begin creating SharePoint apps, we need to set up a development environment. Just as when developing
solutions for previous versions of SharePoint, we will need both a development client to write and compile code and a
server environment in which to test the app.
In SharePoint 2010, it was possible to load SharePoint Server on a client operating system such as Windows 7.
SharePoint 2013 no longer supports this type of installation. You will need to either set up a local server farm with
SharePoint 2013 or use SharePoint Online.
When using a local server farm for app development, you will want to use the new Developer Site Template.
This site collection template includes tips for getting started (see Figure 1-5) and, more importantly, allows for
side-loading of applications. Side-loading is a new feature that allows apps to be deployed directly to a SharePoint
site without first being published to an App Catalog. When deploying an app for debugging, your development
tool can deploy the app directly to a site that uses this template and begin debugging immediately without going
through the normal app acquisition and installation process.
Figure 1-5. Developer Site Template

Exploring the Variety of Random
Documents with Different Content

Nürnberg. Das Abonnement des Blattes, welches alle
Monate erscheint, wird ganzjährig angenommen und beträgt
nach der neuesten Postconvention bei allen Postämtern und
Buchhandlungen Deutschlands incl. Oesterreichs 3 fl. 36 kr.
im 24 fl.-Fuss oder 6 M.
Für Frankreich abonniert man in Paris bei der deutschen
Buchhandlung von F. Klincksieck, Nr. 11 rue de Lille; für
England bei Williams Norgate, 14 Henrietta-Street Covent-
Garden in London; für Nord-Amerika bei den Postämtern
Bremen und Hamburg.
Alle für das german. Museum bestimmten Sendungen auf
dem Wege des Buchhandels werden durch den Commissionär
der literar.-artist. Anstalt des Museums, F. A . B r o c k h a u s
in Leipzig, befördert.

ANZEIGER
FÜR KUNDE DER DEUTSCHEN VORZEIT.
Neue Folge. Siebenundzwanzigster Jahrgang.
ORGAN DES GERMANISCHEN MUSEUMS.
1880. Nº 6. Juni.

Wissenschaftliche Mittheilungen.
Aus Münchener Handschriften.

Woll awff schuler yn dy taffern,
Aurora lucis rutilat.
Lieber gesell, ich trunck alzo gern,
Sicut cervus desiderat.
Vnß ist ein voll vaß auffgetan
Jam lucis orto sydere.
Ich wayß chain peßern auff meinen wan
A solis orto cardine.
Lieber wyrt, gib unß den wein,
Te deprecamur supplices.
Laß vnß trincken vnd froͤ lich sein,
Criste qui lux es et dies.
Gib vns deines brotts ein krost,
Exaudi preces supplicum.
Wyr haben geliden gar grossen durst,
Agrescit omne seculum.
Er warff das glaß an dy wanth:
Procul recedant sompnia.
Der dich hab gemacht, der werd czw schant
Per infinita secula.
Trinck aus der kandel, das ist dein früm:
Inpleta gaudent viscera.
Mein hercz meint, es sey ein am[119]
Quis audivit talia?
Raych vnß den würffel auff den tisch,
Ex more docti mistico.
Dy sagen wer da schuldig ist:
Jubilemus dolio.
Reich mir dy kappen, ich wil beczalen[120]
Te lucis ante terminum.
Ich wyl haim gan geld holen:
Numquam reuertar in perpetuum.
Cod. lat. 15613, saec. XV. (aus Rot), fol. 319.

O socie care, si vis in Suevia stare,
Hec tria sunt que sunt contraria tibi:
Puelle formose, studium valde dolose,
Swartz brot, saur wein, lang quoque weyl.
Panis est niger, in quo stecken die groben cleyen.
Hospicia sunt cara, cum hoc valde amara.
Hec sont in Suevia: si non vis credere, tempta.
Cod. lat. 19657, saec. XV. (aus Tegernsee), f. 87.
Auch die reizende Klage des Hasen, welche Maßmann in Mone’s
Anz. 4, 184 aus Husemanns Sammlung mitgetheilt hat, findet sich im
Cod. lat. 16515 aus S. Zeno bei Reichenhall, f. 182, weniger
vollständig, aber doch auch wieder mit einem neuen, freilich sehr
seltsamen Verse. Es lautet hier:
Flevit lepus parvulus, clamans altis vocibus:
Quid feci hominibus, quod me secuntur canibus?
Nec in orto perveni neque caules comedi,
Nec reginam supposui neque habere volui.
Domus mea silvus (sic) est, lectus meus rubus est,
Leves pedes habeo, caudam parvam habeo.
B e r l i n . W. W a t t e n b a c h .

Feldarbeit und Spinnen im 14. Jahrhundert.
Die hier wiedergegebene Abbildung zeigt uns einen Mann, mit
der Hacke das Erdreich lockernd, der bei nackten Beinen nur mit der
Tunica bekleidet ist, die er des bequemeren Arbeitens wegen
aufgeschürzt hat. Bei ihm sitzt eine Frau in der Haustracht, mit der
Spindel spinnend, während sie den Hanf an einer Kunkel befestigt
hat, die auf einem Fußgestelle neben ihr steht. Zu ihren Füßen liegt
ein Kind in der Wiege. Die Tracht der Frau zeigt, daß wir es
keineswegs mit Leuten der untersten Volksschichten zu thun haben,
auch die Tunica des Mannes, welche ihrer Länge wegen geschürzt
werden mußte, zeigt den Mann besserer Stände, der sein eigen
Gartenland bearbeitet und es sich bequem gemacht hat. Die Scene
stellt Adam und Eva nach der Austreibung aus dem Paradiese dar
und ist einer Reihe von Bildern auf Pergament gemalt entnommen,
welche ehemals den Kopf jeder Seite eines sorgfältig illustrierten
Speculum humanae salvationis bildeten, bei denen jedoch der Text

durchweg abgeschnitten ist. Die Folge trägt die Nummer 5970 der
Bibliothek des germanischen Museums und gehört dem 14.
Jahrhundert an.
N ü r n b e r g . A. E s s e n w e i n .

Der Marktplatz einer Stadt.
F e d e r z e i c h n u n g a u s d e r Z e i t um 1500.
Unter den Handzeichnungen des germanischen Museums
befindet sich auch als Nummer 52 die hier wiedergegebene
Federzeichnung aus dem Schlusse des 15. Jahrhunderts, welche uns
ein sehr ansprechendes Bild aus dem Leben einer Stadt zeigt.
Besonders fällt uns der würdevoll einherschreitende Mann im
Vordergrunde auf, dem ein Junge das große Schwert nachträgt.

Leider ist das mit einem Dache versehene Fuhrwerk zu flüchtig
gezeichnet, so daß wir es dahin gestellt sein lassen müssen, ob wir
recht haben, darin eine große Büchse zu sehen, die dort bereit steht,
jedem der Stadt etwa drohenden Feinde entgegengeführt zu
werden. (Die Perspektive ist wohl verstanden). Daß einzelne Häuser
etwas schief stehen, kann ebensowohl Folge der Flüchtigkeit des
Zeichners sein, als es der Natur entnommen sein kann.

Vorlage für ein Glasgemälde vom Beginne des
16. Jahrhunderts.
Unter den Handzeichnungen des Museums befindet sich als
Nummer 5 die Vorlage für ein Glasgemälde, das Wappen des Kaisers
darstellend, welche in A. Dürer’s Weise gezeichnet ist. Das Blatt ist
rings um nach dem Kreise des Randes ausgeschnitten, so daß das

Monogramm, welches Dürer selbst jedenfalls auf dem Blatte
angebracht hatte, wenn es von ihm herrührte, abgeschnitten ist.
Wenn aber auch das Blatt deshalb nicht, ohne Anfechtung
befürchten zu müssen, des Meisters Namen beanspruchen darf, so
ist es doch eben so schön erdacht, als vorzüglich heraldisch
gezeichnet und deshalb auch heute noch eine vorzügliche Vorlage,
für welche uns wohl einer oder der andere Freund dieses Blattes
dankbar sein dürfte, der etwa eine bunte Scheibe in sein Fenster
einfügen lassen möchte. Der Durchmesser des Originals beträgt 29,7
cm., welches Maß auch ungefähr jenes des Glasgemäldes selbst
gewesen sein dürfte, das wohl auf keinen Fall größer als 30 cm.
werden sollte.

Musicierende Engel von Virgil Solis.
Ein Blättchen, mit der Feder in lichtem Roth und Grün gezeichnet,
Nr. 77 der Handzeichnungen des germanischen Museums, trägt das
Monogramm des Virgil Solis und die Jahrzahl 1562. Es ist ein höchst
liebenswürdiges Bildchen, diese zwei kleinen, im Grase sitzenden,
geflügelten Knaben, welches allerdings in der schwarzen
Wiedergabe, die auf photographisch-chemischem Wege erfolgt ist, in
einzelnen Theilen sich härter darstellt, als in dem lichten, die
Körperfarbe gut wiedergebenden Roth, das aber, gleich den vielen
Stichen, des Meisters Begabung für dekorative kleine Werke
erkennen läßt.

Ein poetischer Fluch.
In einem handschriftlichen Kalendar aus dem 15. Jahrhundert,
das sich in der bischöfl. Seminarsbibliothek zu Brixen befindet,
stehen am unteren Rande des vorderen Deckelblattes nachfolgende
Verse. Die Verszeilen sind nicht abgesetzt. Jemand, der am Inhalte
Anstoß nahm, hat das Ganze durchstrichen, wodurch das Lesen der
ohnehin ziemlich flüchtigen Schrift sehr erschwert wird. Der
Verfasser ist unbekannt.
er hat sein zunge geweczet[121]
meine veinde auf mich geheczet[122]
wider got hazzet er mich
herre selbe tue dein gericht[123]
brich im seine tag abe
ain ander seinen reichtum habe
ain witwe werd sein weip[124]
in sünden sterbe sein leip
seine chind werden waisen
vnd komen nymer aus fraysen
sein gewin ain ander vberhant
der nem im leip[125] leut vnd lant
zu seiner zcswen[126] seiten
ste der teufl zu allen zeiten
der luft im veind werde
verslinden müz in die erde
zu einem fluch werd ihm sein gebet
. . . er . . . . .[127]
I n n s b r u c k . O s w a l d Z i n g e r l e .

Lieder aus der Zeit der Türkenkriege.
Was ich in Folgendem mittheilen will, sind „Vier schoͤ ne neue
Weltliche Lieder / das Erste: Jaͤ gerl bist drina / komb a kleine Weil
heraus / etc. Das Ander: Still / still hoͤ rts mir a wenck zue / ich bin a
Bayrischer Bue / etc. Das Dritte: Gruͤ ß dich Thomerl / Veilt[128], Hießl
seyts mir alle Gott etc. Das Vierdte: Wer da / wer da / wer kombt
vor die Zelten zur Nacht / etc. Jedes in seiner eignen Melodey zu
singen. Gedruckt in disem Jahr“.
So lautet der Titel der zwei unpaginierten Doppelblätter in
Kleinoctav, welche mir vor einiger Zeit im Archive der Familie von
Kripp unterkamen. Sie mögen wol selten geworden sein und schon
darum eines neuen Abdruckes nicht unwerth. Ditfurth („die histor.
Volkslieder des österreich. Heeres v. 1638–1849“ und: „die histor.
Volkslieder des bayer. Heeres v. 1620–1870“) hat sie nicht gekannt.
Der Verfasser dieser Lieder ist unbekannt, und es wäre wol eitle
Mühe, demselben nachzuforschen; jedenfalls war er ein Bayer. Den
Druckort zu bestimmen, würde eine Vergleichung der Typen, sowie
der Titel- und Schlußvignetten mit anderen Druckwerken jener Zeit,
die etwa aus bayerischen Offizinen hevorgegangen sind,
ermöglichen; doch will ich hier nur die wichtigere Frage um die Zeit
der Entstehung, resp. des Druckes, zu erledigen suchen, was in
diesem Falle nicht schwer ist. Schon ein flüchtiger Blick zeigt, daß
wir es mit der Zeit der Feldzüge Prinz Eugens gegen die Türken zu
thun haben. Dem gewaltigen Feldherren galten sie zwar nicht in
erster Linie, sondern dem „großen und kleinen Bue“ des Kurfürsten
Max Emanuel oder, besser gesagt, dem „Churprinzen“; aber Eugen
wird zum öftern, immer mit größter Begeisterung, genannt, und im
ersten Liede ist unter dem „Prinzen“ stets er zu verstehen. Der
Kurprinz Karl Albrecht ist es also, der im Vordergrund steht.
Am 29. November 1716 hatte Max Emanuel an Eugen ein
Schreiben gesandt, worin er diesen zu den Erfolgen des
abgelaufenen Feldzuges beglückwünschte und zugleich die Bitte
stellte, er möchte seinen Söhnen beim Kaiser die Erlaubniß, nach

Wien zu kommen, erwirken, damit sie sich für die „empfangenen
Gnaden und gute Erziehung“ bei Karl VI. persönlich bedanken
könnten. Der Wunsch wurde ihnen gewährt, und auf ihre Aufnahme
in der „Wiener-Stadt“ beziehen sich vielleicht die letzten Zeilen von
II, 4. Mit dem kaiserlichen Heere zogen die beiden Prinzen dann
nach Ungarn, um sich, wie andere Fürstensöhne, die der glänzende
Stern Eugens angelockt hatte, am Kampfe gegen die Türken zu
betheiligen. Ihrem tapferen Benehmen wird in vorliegenden
Gedichten das wärmste Lob zu Theil.
Bemerken wir noch, daß es I, 5 heißt: „fertn[129] habs gseha zu
Peterwardein,“ — diese Schlacht fand am 5. August 1716 statt — so
ergibt sich als Abfassungszeit das Jahr 1717 oder bestimmter, da
Belgrad nach I, 6 und III, 5 schon in den Händen Eugens war, die
Zeit nach dem 22. Aug. d. J. Bald nachher müssen diese Lieder
ihrem ganzen Charakter nach erschienen sein.
Neben den genannten hervorragenden Persönlichkeiten wird
noch Alexander v. Würtemberg I, 3 erwähnt, der im vorhergehenden
Jahre als kaiserl. Feldmarschall in der Schlacht zu Peterwardein und
darauf bei der Einnahme von Temesvar Treffliches geleistet hatte;
III, 3 bezieht sich auf dessen Theilnahme am Kampfe um Belgrad, in
welchem er die Infanterie im Centrum befehligte. Die Erstürmung
dieser Festung durch Max Emanuel als Oberkommandierenden des
kaiserl. Heeres war am 15. August 1688 erfolgt.
Das letzte Lied nun schlägt in jeder Beziehung einen ganz andern
Ton an. Da erscheint plötzlich gewaffnet Cupido, der mit seinen
Pfeilen eine Schildwache attaquiert. Nächst dem ersten scheint mir
dies das gelungenste zu sein. Zum Titel muß ich noch bemerken,
daß die Melodie dem Texte nicht beigesetzt ist.
D a s e r s t e L i e d .
1) Jaͤ gerl bist drina / mein[130] komb a kleine Weil heraus / thue dich
nit lang bsinna gengma[131] ins Wirthshauß / trinck ma beym Adler
/ sauffen dort / ist nur glei a Freud / trinck ma a Maͤ ßl / vergeht
uns (die) Zeit.

2) Meinthalbn kombst glei recht / hab zu dir hinunter woͤ lln gehn /
han dich wol gseha beym Thomerl stehn: Bue du kanst loͤ sen/ es
hat unser Peta Steffel / Muͤ llna Bue / aus Ungarn gschriba / was
sagst du darzue.
3) Was werd ich sagn / schreibt halt daß unser Printz der Held / und
Alexander vorm Jahr im Feld / so tapffer gfochten: das wißma ohn
alles schreibn schon / das Printz Eugeni ein tapffrer Mann.
4) Was mainst mein Brueda / ich denckma offt haimbla bey der
Nacht / daß halt so graußla[132] muß seyn bey der Schlacht / ich
waiß wies zugeht / wann die Baurnbuebn raffa[133] mit einand /
ich kam vor Schroͤ cka glei von Verstand.
5) Namla[134] ists graußla / schlagn da wie der Donner alle drein /
fertn habs gseha zu Peterwardein / hoier wirds erst stincken /
wann die Roßschwaiff her hencken / bitt umb Gnad / bleib da
Strick / Tuͤ rck dir / und uns Belgrad.
6) Jaͤ gerl geh bring maß[135] / gsunds Printzen[136] / alle Herren
Officier / es leben die Reuta / und Musgatier / es sieg Eugeni /
(got) staͤ rck seine Waffen / es gruͤ ne seine Treu / Belgrad lebt nun
von Türcken frey.
D a s a n d e r L i e d .
1) Still / still hoͤ rts mir a wenck zue / ich bin a Bayrischer Bue / wists
was ich will handthiern / ich will ins Feld marschiern / und will in
Ungarland / gleich zur Hand / mein Gluͤ ck probiern.
2) Ich bin allein nit allhier / seynd etli tausend bey mir: unsers
Chufuͤ rsten Bue / der Groß / der Klein darzue / haben sich ghalten
doll[137] / uͤ berall / gschlagen braff zue.
3) Frisch auf du Bayrischer Bue / sprechma der Kandl jetzt zue / ihr
Bayrn unverzagt / der Printz hats schon gewagt / Er steht bey der
Armee / kleinen Weeg / von Belgrad.
4) Er hat nit vil Mann verlohrn / heist das die Tuͤ rcken nit gschorn /
ihr Bayrn renoviert/ das Lob so euch gebuͤ hrt das ihr in Wienner-

Stadt / in der That / habt meritirt.
5) Ains haͤ tt mi nambla bald gschroͤ ckt / d’Hoͤ ppin[138] fieng’s
zannen[139] an / und mi kambs a bald an / afft kam der Richter
her / ungefehr / redt mich scharff an.
6) Frisch auf du Bayrischer Mann / rauffen mir’s[140] Doͤ rffl zusamb /
streiten vors Oesterreich / Gott geb ein guten Streich / es lebt der
Teutschen Muth / Bayren-Blut / keiner nicht weich.
7) Es leb der Kayser der Held / all Officier in dem Feld / Granadier /
Musgatier / Dragoner / Kuͤ rraßier / Crepier der Tuͤ rcken-Hund /
Groß-Sultan / und Groß-Vezier.
D a s d r i t t e L i e d .
1) Gruͤ ß dich Thomerl / Veitl / Hießl seyts mir all Gott willkomb / han
enck[141] was z’sprocha[142] vons Bayr-Fuͤ rsten Sohn / von unsern
Chur-Printzen / wie daß er so stattla in dem Feld / mitn Tuͤ rcken
gschlagen / wie a tapffrer Held.
2) Bubma er grad[143] halt sein Vatter uͤ berall schier nach: der Maxl
Emanuel auf mein Ayd sag[144] / a junger Schißling thut sich so
fruͤ hzeitla ohni[145] wagn / den Tuͤ rckn Gotts-jaͤ mmerlich den
Gruͤ ndt abzwagn[146].
3) Der Printz Eugeni deß Kaysers liebster General / unsern Chur-
Printzen anfuͤ hrt uͤ berall / hat muͤ ssn helffa dem Alexander Stadt
bombardiern / aufs schoissen / fechten sich exerciern.
4) Glei wie sein Vatta allzeit / ja a maͤ chtiger Mann / Belgrad mit
Stuͤ rmen eingnommen schon / wann Gott das Leben dem Chur-
Printzen lange Jahr verleicht / sein Vatta Maxl kein Haar nit
weicht.
5) Juhe ihr Buebma jetzt gehn ma alle mit einand / jeder sein
Treinerl[147] fuͤ hr bey der Hand / wollma was wagn / weil ma
gwunna Belgrad und Schlacht / last uns flangiern Tag und Nacht.
6) Blaßl thue Pfeiffen / Schalmay und Ditl-Dudl-Sack / mach auf
mein Leib-Stuͤ ckl / Veitl gib den Dack / hab noch zwey Landmuͤ ntz

/ auf zwey gute Maß Bier / gsund unsers Chur-Printzen/ gilt mir
und dir.
D a s v i e r d t e L i e d .
1) Wer da / wer da / wer kombt vor die Zelten zur Nacht? weist nicht
daß loschiret / Amor guberniret / allda allda.
2) Gut Freund / gut Freund / das kanst du wol sehen weil ich klein /
Cupido der Kleine / gewaffnet alleine / solt seyn / solt seyn.
3) Nein nein / nein nein / gewaffnet laß ich niemands ein: thue dich
nur weck trollen / sonst kombt die Patrollen / schlagt drein /
schlagt drein.
4) Ja ja / ja ja / ich dich sambt den deinen nit acht / ich will dich
durchkeulen / mit meinen Liebs-Pfeilen / bist schwach / bist
schwach.
5) Ach weh / ach weh / ich Schildwacht verwundet hier steh /
Cupido der Kleine / gewaffnet alleine / ich geh / ich geh.
6) Kein Gwalt / kein Gwalt / Cupido Liebs-Pfeilen aufhalt: So last uns
dann loben / Cupido erhoben / durch Berg und durch Thal.
Ende.
I n n s b r u c k . O s w a l d Z i n g e r l e .

Samuel Karoch.
Die Handschrift der großh. Bibliothek in Weimar Q 108 (nicht
103), auf Papier natürlich, wie alle dergleichen Manuscripte, aus
welcher wir in Nr. 5 des Jahrgangs 1879 die Verse des Heinrich von
Mellerstadt über den Erfurter Brand mittheilten, enthält den
buntgemischten Inhalt so vieler humanistischer Handschriften des
15. Jahrhunderts, in welcher auch die Ueberlieferung des Mittelalters
noch nicht verschmäht wird, da eine scharfe Sonderung noch gar
nicht eingetreten ist. Vorne eingeschrieben ist ein Inhaltsverzeichniß
von dem Besitzer: „Apicius (?) Sifridi me possidet justo titulo.“
Zwischen den hier verzeichneten einzelnen Stücken sind aber
nachträglich verschiedene Eintragungen gemacht, einzelne auch
vielleicht nur als unbedeutend im Verzeichniß übergangen.
Auf fol. 246 ist in lateinischer und deutscher Sprache die
bekannte Bulle des Papstes Innocenz VIII. vom 28. Juli 1490
eingetragen, durch welche die sogenannten Butterpfennige für den
Bau der Elbbrücke bei Torgau bewilligt wurden, d. h. der Ertrag der
Gelder, gegen deren Erlegung der Genuß der Butter in den Fasten
gestattet wurde, weil doch in Sachsen der Oelbaum nicht gedeihe.
Auf Fol. 287 finden wir nach der Ars memoriae des Jacobus
Publicius folgende künstlich gereimte Verse, welche vielleicht von
S a m u e l K a r o c h[148] sein könnten.
Hora vespertina vicina transibam
Quadam in platea: de ea redibam,
Puellarum cetus ac letus ludebat
Dulceque canebat[149] ac coreas ducebat.
2. Unam mihi elegi ac ei servire,
Cui placere novi ac vovi me scire.
Hec dixit, se timere manere se foris,
Nec habere se locum ad jocum amoris.
3. Hac in spe fit lete valete petitum.

Domus ejus scitur ac itur dormitum.
Quam desiderabam, optabam videre,
Hanc in conclavi notavi jacere.
4. Cautus explorator, orator, accedo.
Ungue pulso blande[150]: „Nephande tu predo!
Cur me inquietas? Quid petas edoce.
Responde: cur poscis?“ „Me noscis in voce.
5. Aperi tu, rosa formosa benigna.
Ecce tu instilla.[151] Ac illa per signa
Me cognoscens, plaudens ac gaudens surrexit,
Clamque per posticum amicum invexit.
6. Stratum quem dilexi perspexi paratum,
Odoribusque florum ac morum ornatum.
Vinum tunc non defuit, sed affuit in auro;
Jaspis et jacinctus est intus cum lauro.
7. Philomena grata parata cantabat,
Alauda decora sonora clamabat.
Ibi fuit lira, et mira tonabant,
Jerula[152] amena tunc plena sonabant.
8. Dulces citariste, o Christe! psallebant
Ubi fuit melos, nec delos[153] habebant.[154]
Pectus meum pectori, os ori jungebat:
„Advenisti care!“ amare que flebat.
9. Illa tunc in hora abs mora dormivi,
Brachiis in albis ac salvis me scivi.
Thorum inde licto,[155] sed victo dolore
„Nunc recede!“ dixit et vixit amore.
Vosche Kethe
Die Unterschrift bleibt dunkel. Mit Sicherheit können wir aber wol
annehmen, daß das ganze Abenteuer nur aus dem Tintenfaß
geschöpft ist. Es erinnert an Samuel, dessen „Congestum de
studente et beano“ zu dem alten Inhalt der Hs. gehört. Es ist das
Stück, dessen Inhalt Th. Muther „Aus dem Universitäts- und

Gelehrtenleben“ (Erl. 1866) S. 9–19 mitgetheilt hat, eine damals
offenbar sehr beliebte, häufig vorkommende Schrift, hier mit der
Unterschrift (f. 326 v.): „Finit congestum per Samuelem Caroth
poetam contextum, quod ob reverentiam alme universitatis Lipsensis
proque prandio Aristotelis poetatus est. Scriptum Moccccolxxo in die
S. Thome mart.“
Dieses Aristotelesmahl war nach Muther ein Schmaus, den nach
der in jedem Semester stattfindenden Magisterpromotion die neuen
Magister ihren älteren Kollegen gaben.
Weiterhin f. 345 finden wir, wie im Münchener cod. lat. 3563, die
„Arenga petitoria“, auch hier fehlerhaft bis zur Unverständlichkeit
geschrieben; doch macht die Vergleichung der beiden Abschriften es
möglich, einen verständlichen Text zu geben, welchen wir aus
Achtung vor diesem merkwürdigen Vorläufer der Humanisten in
Deutschland hier folgen lassen, doch ohne die zahllosen Varianten,
welche nur Lesefehler und Schreibfehler sind, zu berücksichtigen.
A r e n g a p e t i t o r i a .
Incliti domini alme universitatis! Insignis hujus studii rectoris
licencia prehabita, gressus meos ad vos, eximios ac egregios
dominos doctores, dirigo, vestras etiam indesinenter oro legalitates,
tantisper me tollerare velle, quousque obstacula mihi incumbencia
brevi enarrem compendio. Nolo equidem dominacionum vestrarum
aures prolixo obtundere rugitu, quoniam quidem non adeo
pregnantis autoritatis me virum profiteor, ut doctoribus magistrisve
sermociner. Hec, doctores eximii venerandique magistri, que
plurimos a prosperitatis abduxit tramite atque in gurgitem latebrose
voraginis precipitavit, fortuna, privignam suam, quam trans tergum
parturiit, squalidam videlicet erumpnam, truculenter in me sevire
compulit. Que me atroci laniavit morsu ac tam feculenta afflixit
inedia, ut instar odorinseci[156], recisa manu heri sui qui depastus
est, post micas repto. Porro citra annos jam novem vitam istam
incolui inopem: in isto hercle temporis fluxu perpauco fretus sum
solacio. Nihil denique inter fluctivaga seculi diffortunia proficiscens

residuare video preter miseriam, caristiam penuriamque
inenarrabilem. Quamobrem fortunatum ac faustum iter, quo crebro
accinctus extiteram, turgida me non sinit explere egestas, sed pocius
per abrupta gradi concitavit. Inter omnes autem obliquatos tramites,
quos itinerare in terris ausus sum, unam semel conscendi semitam,
vestigiis cujus derelictis in devium declinare contigit, quod confestim
quendam terre in districtum proselitum me traduxit, haut procul a
confinio vel saltem in vicinatu, prout conjecto, territorii hujus, in quo
heu onusta me sarcina depressit. Illic viri strenui rabies pestifera
feroci me conquassavit insultu. Illic tetra fortune caligo inextricabili
me convinxit compede, nexuram cujus cujuspiam terrigenarum
potestas preter Romanum pontificem vel multarum autoritatum
presulem, vel forte nisi crudelis juxta vaticinium Francisci Petrarche
in De remediis utriusque fortune etc. mors depessulet, discingere
nequit. Et quis erit, rogo, eo evadendi modus? nullus ut reor. O
misera fortuna et execrabilis, que in cunctipotentis conspectu
abhominaris, quam inopinate me aberrare fecisti! O fortuna
pestifera, quousque oblivisceris me in finem, quousque jocaris
mecum? Pancis retroactis momentis algamata[157] eufortunii
conscendere rebar: tu autem felicitatis noverca in scabellum me
rotasti perniciose miserie. O nimia vesania suffusa! ausa es inopem
me pedibus pessundare! usquequo fantasiaris, ach turbida tu
scorpione deterior fortuna? Non fortuna sed diffortunium merearis
magis congrue dici; eciam, si tibi juxta genus tuum vocabulum
inpingere dignabor, tunc probabilius Thaidem te nuncupare recensui,
quam fortunam, ut meretricium tibi cedat nomen. O Thais,
tremendum te absorbeat chaos! Quid irritas rerum omnium matrem
naturam, et tibi ipsam cogis adversari? Delectaris in eo, quod robusti
procerique corporis et cordati pectoris adolescens mendicancium
onere perstringitur, ignorans quo divertat. Deteriori autem adhuc
flagicio obtusus exto: sum edepol agresti Thaidis convicio, quod
lacrimans referre perurgeor, ab hac sacra concione sequestratus, a
gremio quoque excellentis almeque universitatis divorciatus, a
gramatis studio recisus, ob ineffabilis videlicet egestatis mee
ludibrium. Quis hominum racionis compos divorcium hoc, precor, non
deplangeret postremos in dies, cum tam lamentabiliter a fimbria

honestissime fotricis sue, universalis scilicet studii, rescinderetur? O
Diogenes philosophorum gener[158], ubi nunc queso es, ut
pacienciam me sectari instruas? In grande mihi ignominium[159]
maximo jam transvoluto tempore defunctus es. O illustrissime
philosophorum princeps, quod pre cunctis rutilantis philosophie
sectatoribus sortiris vocabulum, Arestotiles[160], utinam vesana
caribdis tam furtive te abs nobis non surripuisset! Eciam si
furibundum pelagus transfretare me periclitarique opporteret, relictis
omnibus meis conterraneis unicus post te unicum fretum
transpassando non fatigarer, ut te patrem colendissimum doctoripeta
consulere possem, que orbita mihi aggredienda foret, per quam
provehens[161] huic sublimi atque trabeate congeriei reconciliari
mererer. Heu! quid post te, illustrissime princeps, frustra vocifero, cui
tamen fata diu de ergastulo corporis tui spiritum relaxarunt. Tu
quidem orphanorum pater, alumpnus, ac director omnium
philosophancium egregius, quem sacer hic senatus perhenne, ut te
congrue decet, veneratur, testamentum tarnen statuisti
sempiternum, quod nulla unquam oblivione delebitur, recolitur sed
perpetim. Cujus rei eviternam ob memoriam hii celeberrimi tui
sequaces, quibus id idem legasti, presenti in prandio hoc tuo
ineffabili cum tripudio refocillantur: quorum exul ego Samuel post
reliquias fragmentorum, haut solum naturalis cibi, sed et salutiferi
dogmatis serpo, et o utinam eisdem me reficere dignarentur
exilibus[162]. (Satis est.) Solius astripotentis intererit progressum rei
transformare fortunatum[163] in eventum. Appocopato jam modulo
negocium complecti arbitror breviori eciam cursu, quam institueram
obtruncare sententiam, ut tam importunam istam inopiam, qua
conjunctus sum, aliquantisper mitigare[164] valeam. Eximios vos
profecto ac egregios dominos doctores et licenciatos, quos
cunctipotens rerum fabricator diversarum facultatum fulcimento
irroravit, pneumatis quoque sui illustracione corda vestra inflammare
dignatus est, nec non preclare propaginis generosum dominum
comitem Jeronimum Sligk, una cum nobili ac strenuo domino milite
Georgio etc. venerabiles extunc pariter et reverendos facultatis
arcium magistros, postremo sagaces nec ne[165] sollertes hujus feste
civitatis Lipcensis magistrum civium suo presigni cum senatu, ast

eciam omnes simul ac universos commendabiles dominos meos
Arestotilico hic contubernio publice accumbentes, incurvato genu,
pollice flexo, precordiali denique quo potero precatu supliciter oro,
quatenus ob respectum confidencie, que gnaris[166] me
dominacionibus vestris sine dubio amussim constrinxit, aliquid
opitulaminis largiri mihi denegare non velitis. Finitim autem me
ipsum huic sacre concioni uti calculum obsequialem ad dirigendum
trado: vestrum erit, vira prestantissimi, incomptam meam deinceps
regulare inerciam.
Hec est exhortacio, quam Samuel Caroch peroravit coram rectore
universitatis totaque universitate almi studii Lipcensis in prandio
Aristotilis Anno Moccccolxvjo etc. 1470 etc.
Die letzte Zahl bezeichnet das Jahr, in welchem die Abschrift
gemacht ist, deren Schreiber zur Belohnung eine reichliche Tracht
Schläge wohl verdient hätte. Was eigentlich Samuel in’s Unglück
gestürzt hat, bleibt dunkel; wir müssen uns mit der Andeutung
begnügen.
B e r l i n . W. W a t t e n b a c h .

Ein Breslauer Goldschmied im Dienste des
Kurfürsten August von Sachsen.
Der Goldschmied To b i a s W o l f f zu Breslau wird in einem
Briefe vom 22. Januar 1574 von dem Kurfürsten aufgefordert, sich
mit seinen Geräthen an den Dresdener Hof zu begeben, da man
eines Künstlers bedürfe, der mit „Possirung, Schneidung und
Abgießung der Contrafacturen“ wohl vertraut wäre, und der
Hofgoldschmied und Gießer J o a c h i m ihn als die geeignete
Persönlichkeit bezeichnet habe. Der Künstler siedelte in der That in
die sächsische Residenz über und verfertigte „etliche Contrafaituren
der Päbste“, welche in einer versiegelten Schachtel an Hans
Aggelfelde am 9. April 1576 von Torgau aus übersandt wurden, mit
der Weisung, dieselben zu andern Contrafaiten, Münzen und
Schaugroschen in gute Verwahrung zu nehmen, damit man
dieselben jederzeit zu finden wisse. (Dresd. Hauptstaatsarchiv, Cop.
384, f. 152 b. u. 413, f. 80 b.) Vielleicht dient die Mittheilung an
diesem Platze dazu, dem Verbleib der bezeichneten Arbeiten des
Breslauer Meisters an Ort und Stelle (vermuthlich befinden sie sich
noch im Münzkabinet oder in der Kunstkammer) nachzuforschen.
Ueber den Verfertiger ist sonst nur bekannt, dass er 1561 an den
Hof Herzog Georg’s II. von Brieg für ähnliche Aufträge wie nach
Dresden berufen wurde. (Leuchs, bildd. Künstler, S. 24).
B u n z l a u . Dr. E w a l d W e r n i c k e .
Verantwortliche Redaction: Dr. A . E s s e n w e i n. Dr. G . K . F r o m m a n n.
Verlag der literarisch-artistischen Anstalt des germanischen Museums in Nürnberg.
Gedruckt bei U . E . S e b a l d in Nürnberg.
(Mit einer Beilage.)

Welcome to our website – the ideal destination for book lovers and
knowledge seekers. With a mission to inspire endlessly, we offer a
vast collection of books, ranging from classic literary works to
specialized publications, self-development books, and children's
literature. Each book is a new journey of discovery, expanding
knowledge and enriching the soul of the reade
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.
Let us accompany you on the journey of exploring knowledge and
personal growth!
ebookultra.com

Pro SharePoint 2013 App Development 1st Edition Steve Wright (Auth.)

Recommended

More Related Content

Similar to Pro SharePoint 2013 App Development 1st Edition Steve Wright (Auth.) (20)

Recently uploaded (20)

Pro SharePoint 2013 App Development 1st Edition Steve Wright (Auth.)