LS应用程序组件文件有多脆弱？ [英] How fragile are the LS application component files?

问题描述

您好，

 

  自从我加入这个论坛以来，我已经把我的注意力集中在LS上并且放弃了我长时间的Visual Foxpro。  我已尽力至少创建一个普遍接受的LS应用程序。  虽然作为我的新手
，我已经注意到有关LS应用程序设计的一些问题和疑问。  需要注意的一点非常重要：

  LS应用程序组件文件非常精彩 

  考虑我在LS应用程序中所做的这些操作:(我实际上没有从中恢复）

  a。在我放置所有组件屏幕和数据库表之后，在我的LS设计中间。我注意到我的两张桌子以
  错误的方式相关。  我修改了关系并运行我的应用程序。  我收到指向这些文件"ApplicationDefinition.Isml"的调试错误。  

b。我决定将表关系重新修改为之前的状态，构建我的应用程序，但仍然存在错误。

c。我得出结论，文件"ApplicationDefinition.Isml"在我的操作过程中被更改了，所以我决定从备份中复制文件并覆盖当前文件。  错误仍然存​​在。

d。我发布了一些有关此事的问题，收集了一些专业意见。  很遗憾，我无法恢复我的申请。

 

考虑到我修改表格关系的初步行动，我相信如果遇到类似的情况，任何人都会做同样的操作。  或者有更好的方法吗？   LS文件有多脆弱？

 

Nante

 

 

解决方案

Hi Nante

以下是一些要避免令人头疼的重要方面。当发生某些事情时，您应该有一个备份，然后对项目执行以下操作：

清洁，重建。

 

架构版本控制

在您构建完成后首次部署了您的应用程序数据，您可能需要对应用程序及其数据模式进行更新。 LightSwitch允许您部署在现有应用程序数据库的顶部–到一个程度。
在发布时，LightSwitch将读取现有已发布数据库的模式，并尝试仅部署差异，例如添加表，关系以及添加或更改列。

是LightSwitch不会部署的一些更改，因为这些更改可能会导致数据丢失。以下是可能在LightSwitch实体设计器中进行的一些重大更改，这些更改可能导致无法部署架构
更新。

• 
  
  重命名实体属性

Hi,

 

 Ever since I joined this forum, I've already set my focus to LS and set aside my long time Visual Foxpro.  I've tried all my best to at least create a generally accepted LS application.  Though as novice as me, I've noted some problems and questions along the way regarding LS application design.  One very important to note is:

 LS APPLICATION COMPONENT FILES ARE VERY DELICATE  

 Consider these operations I've made in my LS application:(I didn't actually recovered from this)

 a. on the middle of my LS design, after I laid all my component screens and database tables. I've noticed that two of my tables were related in a  wrong way.  I modified the relationship and run my application.  I got a debugging error pointing to these file "ApplicationDefinition.Isml".  

b. I decided to re-modify the table relationship to the previous state, build my application but, still the error persist.

c. I concluded that the file "ApplicationDefinition.Isml" was changed during the course of my operation, so I decided to copy the file from my backup and overwrite the current one.   Again the error persist.

d. I posted some question regarding the matter, gathered some professional advice.  Unfortunately, I was not able to recover my application.

 

Considering my initial action on modifying the relationship of my tables, I believe any one would do the same operation if they encounter similar situation.  Or is there a better way to do it?  How fragile are LS files?

 

Nante

 

 

解决方案

Hi Nante

Here are some important aspects to keep in mind to avoid headaches. When something that happens, you should have a backup, and then do the following to the project:

Clean, Rebuild.

 

Schema Versioning

After you’ve built and deployed your Application Data for the first time, you may need to make updates to the application and to its data schema. LightSwitch allows you to deploy over the top of an existing Application Database – to a degree. At publish time LightSwitch will read the schema of the existing published database and attempt to deploy just the differences, for example adding tables, relationships, and adding or altering columns.

There are a number of changes that LightSwitch will not deploy because the changes could result in data loss. Here are some of the breaking changes that could be made in the LightSwitch Entity designer that could result in being unable to deploy the schema updates.

• Renaming an entity property

这篇关于LS应用程序组件文件有多脆弱？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！